There is no test on my side that has passed without crash since June 18th.
There is also a problem with the Google Play Game Services from time to time, but I got an answer about it here:
Iām not unity developer but iām facing the same issue in my app and canāt update my app on the store
Exception java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.Class java.lang.Object.getClass()' on a null object reference
at android.os.Parcel.createExceptionOrNull (Parcel.java:3189)
at android.os.Parcel.createException (Parcel.java:3167)
at android.os.Parcel.readException (Parcel.java:3150)
at android.database.DatabaseUtils.readExceptionFromParcel (DatabaseUtils.java:202)
at android.database.DatabaseUtils.readExceptionFromParcel (DatabaseUtils.java:154)
at android.content.ContentProviderProxy.call (ContentProviderNative.java:764)
at android.content.ContentResolver.call (ContentResolver.java:2466)
at android.content.ContentResolver.call (ContentResolver.java:2446)
at ekfr.a :)com.google.android.gms@242013038@24.20.13 (190400-633713831):29)
at com.google.android.gms.wallet.intentoperation.setupwizard.PaymentsSetupWizardAccountChangeIntentOperation.onHandleIntent :)com.google.android.gms@242013038@24.20.13 (190400-633713831):252)
at com.google.android.chimera.IntentOperation.onHandleIntent :)com.google.android.gms@242013038@24.20.13 (190400-633713831):2)
at ajdw.onHandleIntent :)com.google.android.gms@242013038@24.20.13 (190400-633713831):8)
at pbh.run :)com.google.android.gms@242013038@24.20.13 (190400-633713831):70)
at pbg.run :)com.google.android.gms@242013038@24.20.13 (190400-633713831):152)
at elbx.run :)com.google.android.gms@242013038@24.20.13 (190400-633713831):21)
at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:644)
at java.lang.Thread.run (Thread.java:1012)
The issue seems to be caused by the version of Game Mobile Services on the test devices being outdated. Unless the devices are updated to Google Mobile Services v24.22+, the bugs will persist. My solution is to eliminate the three devices where I see crashes - Google Pixel 8, Google Pixel 5 and Motorola G20 - and skip the review. Then I will add the devices again and follow up on the production issues. Hope that user devices will be up to date
Hi Dear,
How to eliminate the devices ?
i have already excluded pixel 8 device from device catalogue but still google testing on it in internal testing track.
do you have any suggestion ?
I tried twice yesterday and confirmed that eliminating devices does not solve the pre-launch report issues. Finally, I reported this to Google.
There seems to be no choice except upload a bulid every day and hope that I donāt run into problematic devices, but on my side it has been like this for 11 days.
I donāt have a single crash free release, itās really crazy. When I add one of the Admob or Google Play Pames plugins to the project, I always see crashes on same device - Google Pixel 8!
We have exactly the same error and preventing us from releasing updates to our applications.
I am not sure if it is related to Unity or is it the test devices of Google that is faulty. I think someone should contact Google Play, with minimal project.
Iām experiencing the same issue in my Android Studio project. The error extends beyond Unity or Android Studio; itās a Google issue. In the pre-launch video sent to me after testing my app, I noticed that when the tester clicked on a TikTok banner, a popup dialog appeared, stating that Google Mobile Services needed to be installed or updated.
This indicates that the error is not related to our projects or the development tools we use.
Have made numerous changes trying to resolve the issue, including changing Gradle versions, API levels, and dependencies, but to no avail.
I have the same issue and the game work fine on Google Pixel 8, but on Google Pixel 8 Pro, it has black screen issue.
I made also several build to try to fix the issue, only 1 time it worked and itās when I have clear logs, library and temp folder, but then doing this again, the issue still went back.
It seems to be an issue from the device and we would need to wait them to fix it to have this issue disappearā¦
I didnāt wait for the pre-launch test to complete and sent my app for review. It went live in 10 minutes in Open Testing and Production environments. I will follow up to see if the issues show up on usersā devices.
I was getting this with Unity 2022.3.21f1, targeting Android 33, using Unity In App Purchasing 4.9.4. I upgraded to Unity In App Purchasing 4.12.0 and rebuilt. I ran Firebase Testlab on the resulting aab on a Pixel 8 and it passed.
I am also facing this issue its because of Google play games sdk , I have done so many solutions updating sdks , downgrades there version but no solution