NPE - Expected to unbox a 'boolean' primitive type but was returned null | Voxel Busters | Page 1

high creek Mar 16, 2024, 6:09 AM

#

Hi @zenith lotus
Since updating to v2.7.1 from 2.4.1, we are getting very high crash rate due to this particular issue. This has only showed up in last version where I have only updated the kit as per the instructions. Can you look into it and guide us how to fix this issue?

Here is a stack trace:

Exception java.lang.Error: FATAL EXCEPTION [main]
Unity version     : 2020.3.48f1
Device model      : samsung SM-A715F
Device fingerprint: samsung/a71zh/a71:13/TP1A.220624.014/A715FZHU9DWH4:user/release-keys
Build Type        : Release
Scripting Backend : IL2CPP
ABI               : arm64-v8a
Strip Engine Code : true

Caused by: java.lang.NullPointerException: Expected to unbox a 'boolean' primitive type but was returned null
  at $Proxy25.equals
  at java.util.ArrayList.remove (ArrayList.java:631)
  at com.voxelbusters.essentialkit.cloudservices.CloudServices.onSyncronizeFinished
  at com.voxelbusters.essentialkit.cloudservices.CloudServices$b$a.onSuccess
  at com.voxelbusters.essentialkit.cloudservices.CloudServices$c.onComplete
  at com.google.android.gms.tasks.zzi.run (com.google.android.gms:play-services-tasks@@18.0.2:1)
  at android.os.Handler.handleCallback (Handler.java:942)
  at android.os.Handler.dispatchMessage (Handler.java:99)
  at android.os.Looper.loopOnce (Looper.java:226)
  at android.os.Looper.loop (Looper.java:313)
  at android.app.ActivityThread.main (ActivityThread.java:8762)
  at java.lang.reflect.Method.invoke
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:604)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1067)

zenith lotus Mar 18, 2024, 12:31 PM

#

Can you please share your implementation once?

high creek Mar 19, 2024, 6:46 AM

#

zenith lotus Can you please share your implementation once?

We haven't changed anything in this.

📎 CloudSave.cs

high creek Mar 20, 2024, 5:43 AM

#

The crash rate has increased significantly, from 0.12% to 2.88%. Due to this rise, we're halting the rollout and reverting to VB version 2.4.1. If you have any suggestions for fixing the issue, please share them.

high creek Mar 21, 2024, 6:13 AM

#

@zenith lotus can we get any comments on the issue please?

zenith lotus Mar 21, 2024, 6:20 AM

#

Yes. I was trying to reproduce it but couldn't. May be one specific datatype leading to the issue when getting converted/deserialised.
Can you get me a snapshot of your data in json format so that i can try the exact samething?

high creek Mar 21, 2024, 8:20 AM

#

📎 GameState2

high creek Apr 2, 2024, 11:37 AM

#

high creek Hi <@91622044445208576> Since updating to v2.7.1 from 2.4.1, we are getting ver...

Hi,

This one has entirely gone down after reverting back to previous version we had. We do want to update the kit. Do you have any suggestions on how can we proceed safely without getting the increased crash rate hit?

high creek Apr 17, 2024, 8:00 AM

#

Hi @zenith lotus the AppStore spring deadline is approaching soon. Any leads on this issue?

zenith lotus Apr 18, 2024, 1:08 AM

#

@high creek May I know what is the deadline you are talking about?

high creek Apr 18, 2024, 4:48 AM

#

zenith lotus <@698393895553466411> May I know what is the deadline you are talking about?

The one from Apple: <#📢announcements message>

high creek Jun 10, 2024, 9:07 AM

#

Hi @zenith lotus

We are still experiencing a high crash rate related to the same issue (please ignore my Apple-related comments for now as we want to focus on Android first). This time we tried updating to Unity 2022 LTS, but we are still seeing a very high crash rate. One thing that helped was increasing our interval to stop the parallel synchronize calls from 1 second to 60 seconds. I made this change after reading another thread with a slightly different error: <#1229319465217294377 message>

Although we are calling synchronize on events, increasing the interval before making another call has reduced the crashes by half. Despite this reduction, crashes are still occurring in significant numbers. Almost 90% of the crash events are due to this issue.

I wanted to ask if we should try another build with an even longer interval or if there are any other measures we can take to reduce the crashes. Any ideas would be appreciated. Thanks!

#

Here is the stack trace again:

Exception java.lang.Error: FATAL EXCEPTION [main]
Unity version     : 2022.3.27f1
Device model      : Xiaomi M2102J20SG
Device fingerprint: POCO/vayu_ru/vayu:13/TKQ1.221013.002/V14.0.1.0.TJURUXM:user/release-keys
CPU supported ABI : [arm64-v8a, armeabi-v7a, armeabi]
Build Type        : Release
Scripting Backend : IL2CPP
Libs loaded from  : lib/arm64
Strip Engine Code : true

Caused by: java.lang.NullPointerException: Expected to unbox a 'boolean' primitive type but was returned null
  at $Proxy23.equals
  at java.util.ArrayList.remove (ArrayList.java:631)
  at com.voxelbusters.essentialkit.cloudservices.CloudServices.onSyncronizeFinished
  at com.voxelbusters.essentialkit.cloudservices.CloudServices$b$a.onSuccess
  at com.voxelbusters.essentialkit.cloudservices.CloudServices$c.onComplete
  at com.google.android.gms.tasks.zzi.run (com.google.android.gms:play-services-tasks@@18.1.0:1)
  at android.os.Handler.handleCallback (Handler.java:942)
  at android.os.Handler.dispatchMessage (Handler.java:99)
  at android.os.Looper.loopOnce (Looper.java:211)
  at android.os.Looper.loop (Looper.java:300)
  at android.app.ActivityThread.main (ActivityThread.java:8272)
  at java.lang.reflect.Method.invoke
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:559)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:954)

zenith lotus Jun 10, 2024, 9:16 AM

#

If it's possible to add manual syncronize that would be great. Due to concurrency issues and to simplify the api, we will be handling the auto sync internally and removing the sync timer for android in V3.

high creek Jun 10, 2024, 9:21 AM

#

We are calling CloudServices.Synchronize(); manually on important events. But sometimes we reload scene and it gets called multiple time. That's what the interval is trying to resolve.

#

The sync interval in settings is also set to the default 60

zenith lotus Jun 10, 2024, 9:23 AM

#

set it to 100000

#

As you are syncing manually, you don't need sync timer. This is one of the reasons to remove the sync timer config as it adds extra confusion. Instead if we do it internally when app goes to pause that would be enough - similar to how playerprefs are handled

high creek Jun 10, 2024, 9:28 AM

#

zenith lotus As you are syncing manually, you don't need sync timer. This is one of the reaso...

Right, yeah we are calling it manually on events like OnApplicationFocus so that should work. Increasing the Sync Interval in settings might help in case it gets triggered with our manual call. Hope it brings down the crash rate 🤞

high creek Jun 20, 2024, 6:21 AM

#

Increasing the Sync Interval to 100000 didn't help. Can you suggest any other solution?

We are not getting any complaints from the user and unable to reproduce the crash at our end. As a temporary workaround, would adding a null check help? If so, can you point me where to add it?

zenith lotus Jun 20, 2024, 7:11 AM

#

Increasing the Sync Interval to 100000 didn't help. Can you suggest any other solution?

We are not getting any complaints from the user and unable to reproduce the crash at our end
I see it a bit conflicting. Did I miss something?

I don't see any other specific reasons for it to fail. But we will revisit this in V3 anyways to make sure multiple calls in parallel also are handled.

high creek Jun 20, 2024, 7:15 AM

#

Yeah, it is conflicting as it is showing up as a user perceived crash on Play Store. Usually our player make the noise when we rollout the build in open testing but for these builds, no one seems to complaint about crash or data loss. That's why I was thinking about adding some error handling perhaps on the callback OnSynchronizeComplete

#

I don't think it will be useful, but here is some more context. We recently updated to Unity 2022 LTS from Unity 2020 LTS to support Android 34 as the target API level. The build failed with the older Essential Kit 2.4.1 but works with the newer 2.7.1. However, the crash frequency increases significantly with the update to 2.7.1, and we are unable to roll it out completely due to the above-threshold crash rate (it was below 0.2% and crosses the threshold of 1.09% with Essential Kit 2.7.1).

zenith lotus Jun 20, 2024, 7:28 AM

#

I see.
If you have sync interval to 10k secs, do you have any reports in your closed group?

high creek Jun 20, 2024, 7:35 AM

#

None so far but Play Store crash rate is hanging around bad behavior threshold with 5% production rollout

high creek Jul 2, 2024, 11:06 AM

#

@zenith lotus Why does the kit logs so much when I have set the Log Level to Error? It even prints this when Log Level is None.

📎 message.txt

zenith lotus Jul 2, 2024, 11:25 AM

#

This got fixed in 2.7.2

#

Its actually single data - your saved data but displayed in multiple lines

high creek Jul 2, 2024, 11:34 AM

#

zenith lotus This got fixed in 2.7.2

Ah cool. The asset store is still showing the version 2.7.1

zenith lotus Jul 2, 2024, 12:22 PM

#

2.7.2 is under review.

#

Btw, were you able to reproduce the crash?

high creek Jul 2, 2024, 12:49 PM

#

No, we are temporarily removing the auto cloud sync and giving the players a button to manually sync it. That should defintely bring down the crash rate

high creek Aug 14, 2024, 6:19 AM

#

@zenith lotus I just wanted to update you that the crashes have decreased to normal levels after we increased the interval before another Synchronize() call can be made to 300 seconds. Initially, the interval was 1 second, which worked well with the older version 2.4.1. We then increased it to 60 seconds, which didn't have much effect, but after extending it to 300 seconds, crashes have significantly reduced. While they still occur (around 22% of crashes), we are now well below the bad behavior threshold.

zenith lotus Aug 14, 2024, 7:41 AM

#

high creek <@91622044445208576> I just wanted to update you that the crashes have decreased...

Thanks for updating!
The interval will be removed in V3 and we handle it internally similar to how PlayerPrefs handle.

plain whale Aug 17, 2024, 10:00 AM

#

@high creek I have the same problem but it only occurs after I call Application.Quit(); Are you using Quit in your code? https://discord.com/channels/672868273779507223/1274300750154956853

high creek Aug 17, 2024, 11:21 AM

#

plain whale <@698393895553466411> I have the same problem but it only occurs after I call Ap...

Yes, we are using Application.Quit() for the Android back button in ExoMiner, but from the stack trace you shared, how can you tell that it’s happening during the Quit event?

Just to clarify, we’re still experiencing crashes, but they have decreased significantly after we imposed a 300 second limit before another Synchronize() call can be made. This restriction is in addition to setting the Sync Interval to 100000 in the Voxel Buster Cloud Services settings suggested by @zenith lotus

#NPE - Expected to unbox a 'boolean' primitive type but was returned null