-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Black screen with previously working ARCore apk file #1639
Comments
So you built an apk then run the same APK a few days later and it no longer works. That is odd. Not sure what is happening here. I can't really help much with out logs. Can you run "adb bugreport" add attach the output? Hopefuly it is something obvious that I can help with. The Unity Forum issue you refered to was just when we released ArCore 1.41. We did have problems with that roll out https://github.com/google-ar/arcore-android-sdk/issues/1634 addressed Dec 28. We (ArCore) have not changed anything between Feb 6th though Feb 15th. The only thing locally I can suggest is you might want to try running with adb logcat running and see what happens around the time you see "app is not responding" message. It does sound like something changed on you. Hopefully the logs can show us what? |
Talking to my co-worker there might have been signing bug. If you are using geospatial or cloud anchors and Keyless authorization check here |
Hey @swardle , apologies for the tremendous delay, I took a break from this project (partially due to frustration), but I am now on it full time. I am not using anything related to geospatial or keyless authorization. I am building this app with Unity ARFoundation and building for android. I had it working in January which makes me suspect this is an ARCore issue. I've even factory reset the Google Pixel 7 that I am using for testing, updated to the latest ARCore apk, and the app still kept crashing! I've attached my logcat file. You'll see many lines similar to the following few I'll provide here as an example:
The next step I'll try to take is possibly rolling back to a previous ARCore apk -- if that doesn't work, I'll run a hardware check. I did try this app on an older Samsung s9 running android 10 and the app didn't crash, but hand tracking was not working (I'm using mediapipe). PS: The pixel 7 I am running tests on is using android version 14 Any thoughts and assistance would be greatly appreciated. This issue has halted my entire development process for some time now. |
Humm Well I think this is one of your crashes. I don't see any arcore calls. Looks like you are crashing in unity graphic stack. Maybe the change the effected you is some type of android security update. It looks like it is moving graphic data between the OS and your app maybe given the function names 03-20 08:28:07.233 7393 7422 E AndroidRuntime: at libunity.MemoryManager::GetAllocatorContainingPtr(void const*)(GetAllocatorContainingPtr:24) The PlayerInitEngineGraphics is why I think it is a graphics stack problem. 03-20 08:28:07.233 7393 7422 E AndroidRuntime: at libunity.PlayerInitEngineGraphics(bool)(PlayerInitEngineGraphics:172) Maybe the unity team could help you out? the whole call stack a few different ways as unity prints it out. 03-20 08:28:07.231 7393 7422 E AndroidRuntime: FATAL EXCEPTION: UnityMain |
@swardle Thank you for your insight. There was a security update actually that I'm just now remembering -- this could make sense considering the types of calls you've pointed out. I will trying rolling back to a previous version of android -- like I said, it did work without crashing on the Galaxy S9 running an older version of android (API 29). I'll update you. |
Update: Reverting back to Android 13 from 14 via the bootloader still did not work and the application continues to crash... |
update: It was an error with how Unity was building -- I updated to an LTS version of Unity and had to rewrite the mainTemplate.gradle file and the 'LTS version' of Unity updated some lines once I re-imported the project in the gradleTemplate.gradle file used to build the android application automatically. I can't say I'm familiar with all of the lines that were updated, but if anyone else sees this I implemented the changes in this stackoverflow post: stackoverflow, Unity mainTemplate.gradle @swardle thank you for your assistance, if it wasn't for your redirection I wouldn't have resolved this due to my unfamiliarity with parts of the android->ARCore->ARFoundation -> Unity stack. |
SPECIFIC ISSUE ENCOUNTERED
I had this AR core (made in unity) application working February 6th and today (Feb. 15) I am met with a black screen once I open it as if the app never loads -- I'm met with a "app is not responding" message when waiting and I can choose to wait or close the app. I've uninstalled and reinstalled ARCore to try and fix the issue with no luck. I've also updated to the latest version of android and I've reinstalled the apk and newer apks of the same application and I get the same exact issue.
Users in the following unity forum seem to have reported what I believe is most similar to my issue here, but apparently this was resolved by Google devs this January: Unity Forum, ARCore and ARFoundation
VERSIONS USED
The text was updated successfully, but these errors were encountered: