I'm running into this basic issue while integrating the AppWarp Unity SDK (no version is specified, downloaded on 10 of March) with Unity 4.3.4 Android player.
The AppWarpVikingMobile sample fails with the same error.
"telnet appwarp.shephertz.com 12346" does connect to the server. Wireshark shows no packets (running with a filter "host appwarp.shephertz.com").
There is a similar issue asked here on February, but it is unresolved still.
Seems that it's SDK import/compatibility issue.
Any ideas?
When running in the player you have to use the AppWarpUnity.dll asset. Its only when building the apk to run on a physical device you need to build with AppWarpUnityMobile.dll asset (and NOT AppWarpUnity.dll) along with the native plugins provided.
It can be a bit confusing because Unity has different restrictions on different versions (Pro and Free) for different platforms with regards to plugins and sockets. AppWarp's goal is to give developers a way to use it with or without the Unity Pro on all platforms.
The interface exposed by the assets is the same so your application code need not change.
Related
Hellow
I tried to get device information from mobile build version with Unity framework.
Calling the CreateAVideoDeviceManager(), CreateAAudioRecordingDeviceManager(), CreateAAudioPlaybackDeviceManager() apis always results in false. So the device information cannot be displayed.
However, in the standalone version, it works normally.
Do you have any solution for the above issue?
VideoDeviceManager and AudioDeviceManager are designed for standalone desktop environment only. It is in the documentation.
Trying to follow the Microsoft Azure Spatial Anchors tutorial (even after it was recently updated) but the Release build of the project crashes on launch on the device (just after the Unity splash screen). Interestingly a Debug build of the same project seems to launch ok.
I've been able to build, deploy, test both the basic Hololen2 tutorials and the ASA Samples as well as some custom projects so don't think this is a general development or deployment issue.
Have others been able to follow this tutorial and successfully deploy to a device recently and/or is there any suggestions to diagnose the issue further?
Setup and Unity packages used (as per the tutorial and linked instructions):
Hololens OS (up to date): 19041.1136
Unity 2019.4.19f1
com.microsoft.azure.spatial-anchors-sdk.core#2.7.1
com.microsoft.azure.spatial-anchors-sdk.windows#2.7.1
MRTK Foundation - 2.5.3 from the basic tutorial series (MRTK Package Tool)
AR Foundation: 3.1.3
Windows Mixed Reality: 4.2.1 (downgrade from 4.2.3?)
MRTK.HoloLens2.Unity.Tutorials.Assets.GettingStarted.2.4.0.unitypackage
MRTK.HoloLens2.Unity.Tutorials.Assets.AzureSpatialAnchors.2.4.0.unitypackage
Note: MRTK.HoloLens2.Unity.Tutorials.Assets.AzureSpatialAnchors.2.4.0.unitypackage listed in the tutorial actually links to a new 2.5.3 package (https://github.com/microsoft/MixedRealityLearning/releases/tag/azure-spatial-anchors-v2.5.3) however the version file in this package still has 2.4.0??
Exception thrown at 0x00000226E0FBCC40 in Workspace Hololens2 MRTK.exe: 0xC0000005: Access violation executing location 0x00000226E0FBCC40.
Have you tried to upgrade the ASA SDK to version 2.7.2 (https://github.com/Azure/azure-spatial-anchors-samples/releases/tag/v2.7.2)?
They have recently fixed an error exactly like the one you're reporting:
"The first bug was specific to ARM32 builds running on HoloLens 2 and was manifesting as an access violation crash in SDK during anchor creation or query."
I have the same Problem. Running it without the Debug Window worked for me!
I have a Unity project that I'm switching from APKs to AABs (app bundles). Previously, when I was building it as an APK, the Google Play Console told me the APK was 64-bit compliant.
Now that I'm building an aab, I'm getting the warning:
This release is not compliant with the Google Play 64-bit requirement.
The following APKs or App Bundles are available to 64-bit devices, but
they only have 32-bit native code
I have both ARM7 and ARM64 architectures set.
I am excluding x86.
When I open the .aab in an archive viewer, the lib folder has all of
the .so's for both arm64-v8a and armabi-v7a.
I'm using IL2CPP, .NET 4.x
I'm using Unity 2018.3.7f1
My ndk version is 16b
My
Android Studio is up to 3.4.2 and gradle is 3.2
A lot of similar threads here talk about following the "Learn more" links, which I've done. I had already done all of the work to get my app 64-bit compliant before switching to app bundles.
Other threads talk about Android Studio solutions, which I can't use because my automated build process involves building with Unity from command line, so it has to be Unity configurations or bust.
My expectation was the app bundles were supposed to be the hot new way to let Google build better APKs for you, but it seems like it's getting confused on whether or not aabs are actually 64-bit compliant, which seems to defeat the whole purpose.
Is this a Unity problem, does Google have an error in their system with regards to app bundles, or is there some other step I'm missing?
For those who have this problem since yesterday (August 19, 2019):
In Player Settings > Other Settings you must now uncheck the x86 box (It is for the 32-bit Intel architecture).
You will now only have the following warning:
The device types on which your application can be installed will be more restricted.
But, in my case, it drops from 12392 devices to 12385 devices.
Here is the opinion of a Unity member on the issue:
x86 is used by less than 0.4% of all Android devices, so it shouldn't have any real impact.
x86 target will be removed completely in Unity 2019.3.
It looks that there was a bug in the Play Console where this message was displayed even when the AAB was compliant. This should have been fixed last Friday afternoon.
Try again now.
Got following stacktrace from Android Vitals:
java.lang.Error: FATAL EXCEPTION [main]
Unity version : 5.6.2f1
Device model : samsung SM-G955F
Device fingerprint: samsung/dream2ltexx/dream2lte:8.0.0/*****/***********B7:user/release-keys
Caused by
at bitter.jnibridge.JNIBridge.invoke (Native Method)
at bitter.jnibridge.JNIBridge$a.invoke (Unknown Source:20)
at java.lang.reflect.Proxy.invoke (Proxy.java:913)
at $Proxy1.onBindingDied (Unknown Source)
at android.app.LoadedApk$ServiceDispatcher.doConnected (LoadedApk.java:1652)
at android.app.LoadedApk$ServiceDispatcher$RunConnection.run (LoadedApk.java:1685)
at android.os.Handler.handleCallback (Handler.java:789)
at android.os.Handler.dispatchMessage (Handler.java:98)
at android.os.Looper.loop (Looper.java:164)
at android.app.ActivityThread.main (ActivityThread.java:6938)
at java.lang.reflect.Method.invoke (Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run (Zygote.java:327)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1374)
Have no clue. Any help or explanation will be welcome.
We were seeing the same error out of a large portion of our player base. We were able to contact Unity and get some insight into the error.
From Unity Enterprise Support:
We are aware of the issue. We fixed it in 2017.3 after upgrading the
JNIbridge to support Oreo APIs. Previous reports describe that when a
Unity application that has INTERNET permission is running, and the
Google play services is updated, stopped or reboot, it will cause the
app to crash in Android 8, 8.1 devices.
The problem is that ServiceConnection.onBindingDied which was added in
API level 26 is not implemented before 2017.3; we added this for
GoogleAdsServiceConnection in such version an also updated the
JNIbridge to solve the problem.
I'm able to reproduce it in an empty project by setting Internet
Access to "Require" and when running on the device, go to settings
->Apps & notifications->google play services->storage->MANAGE SPACE->CLEAR ALL DATA, then the app crashes as described in Stack
Overflow.
Do you have plans to upgrade your project to 2017.4 LTS?
I'm asking because we think that a backport of the fix is not
feasible, not only because it would be for a version for which we no
longer create patches (5.6.x) but an appropriate fix would involve
backporting the full support for Oreo APIs which might be tricky and
may cause regressions.
We have decided to try and upgrade our Unity Version from 5.6.4f1 into the recommended 2017 versions. Sounds like it should resolve our issues.
Today for our project in Android Vitals for users on Android 8.0 and 8.1 began to display the same failure. We use Unity 2017.1.3 Maybe it does not depend on the version of Unity. I found some correlation of the occurrence of such a failure with the release of updates for Google Play Market.
UPDATE:
We were able to reproduce this error on our Android 8.1 device:
Launch the application on the device.
Force Google Play Market to stop.
Try to purchase IAP in the store.
Watch the specified error report in Android Vitals
Given the peculiarity of this error to appear unexpectedly and massively, and then also unexpectedly disappear completely without making changes to the application, we concluded that the system service stops forcibly when the background of the Google Play Market is updated for users with auto-update enabled and connecting to the WiFi network during use our application and then try to access the data or conduct an operation with IAP in the Google Play store.
We have managed to reproduce the bug on Android 8.0 with Unity 2017.2.1.
Upgrade to Unity 2017.4.7 LTS has fixed the issue.
Can you please tell me, if vuforia can run on a PC? I have tried to make an .EXE file, but it does not work.
Please tell me how can I run vuforia apps on my PC? Should I build it for Windows store using Unity and then run it on Windows 8?
Can you please tell me vuforia can run on pc
Answer is No. You cannot build windows or mac app with Vuforia. Vuforia is only supported on Mobile Platforms (iOS, Android).
But you want to test on Windows, you can run your app and test in unity Editor mode with webcamera attached. I hope it will answer your question.
download unity from the unity website , install & run
download vuforia and vuforia sample for unity on vuforia website
create unity project and add vuforia package to the project
There are some tutorials for you for importing the samples and ofcourse you need to get a key with the name of your project.
Have a look at this https://www.youtube.com/watch?v=HnjbTytHH6U
For now, and without plugin, the answer is no. But,
Vuforia is work on supporting win 10, so maybe months later, you can develop a win 10 universal app.
There is some plugin support build the app for windows and Mac, it costs much money. The plugin is provided by maximarouf
As the answers above, I agree that it is enough to run in unity editor for presantation and test.
Vuforia now has a Windows 10 Early Access Program. You can apply for participation and may get access to the Windows 10 UWP SDK.
However, it currently only supports Intel based devices, like the Surface Book and Surface Pro series.
Alternatively, you can use the Unity3D Plugin to build an app which works on Windows.
No vuforia is not supported . U will get Vuforiawrapper.dll missing error when you try to .
Instead what you could do is , make an APK , Download Bluestacks and install it in PC and emulate your vuforia app in PC . But no Vuforia is not made for PC. It supports UWP though which means Windows Tablet , Windows Phone, Hololens .