Skip to content
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

Crashes because No NameTypeIndex match for LONG_STANDARD #92

Closed
fanjavaid opened this issue Jun 21, 2023 · 4 comments · Fixed by #93
Closed

Crashes because No NameTypeIndex match for LONG_STANDARD #92

fanjavaid opened this issue Jun 21, 2023 · 4 comments · Fixed by #93

Comments

@fanjavaid
Copy link

fanjavaid commented Jun 21, 2023

Hello, I had implemented fingerprintjs-android 2.0.0 and got crashes about TimeZoneNames with following details:

Fatal Exception: java.lang.AssertionError: No NameTypeIndex match for LONG_STANDARD
       at android.icu.impl.TimeZoneNamesImpl$ZNames.getNameTypeIndex(TimeZoneNamesImpl.java:724)
       at android.icu.impl.TimeZoneNamesImpl$ZNames.getName(TimeZoneNamesImpl.java:790)
       at android.icu.impl.TimeZoneNamesImpl.getTimeZoneDisplayName(TimeZoneNamesImpl.java:183)
       at android.icu.text.TimeZoneNames.getDisplayName(TimeZoneNames.java:261)
       at java.util.TimeZone.getDisplayName(TimeZone.java:405)
       at java.util.TimeZone.getDisplayName(TimeZone.java:322)
       at com.fingerprintjs.android.fingerprint.info_providers.DevicePersonalizationInfoProviderImpl$timezone$1.invoke(DevicePersonalizationInfoProvider.kt:46)
       at com.fingerprintjs.android.fingerprint.info_providers.DevicePersonalizationInfoProviderImpl$timezone$1.invoke(DevicePersonalizationInfoProvider.kt:46)
       at com.fingerprintjs.android.fingerprint.tools.ExceptionSafeExecutorKt.executeSafe(ExceptionSafeExecutor.kt:9)
       at com.fingerprintjs.android.fingerprint.info_providers.DevicePersonalizationInfoProviderImpl.timezone(DevicePersonalizationInfoProvider.kt:46)
       at com.fingerprintjs.android.fingerprint.fingerprinting_signals.FingerprintingSignalsProvider$timezoneSignal$2.invoke(FingerprintingSignalsProvider.kt:322)
       at com.fingerprintjs.android.fingerprint.fingerprinting_signals.FingerprintingSignalsProvider$timezoneSignal$2.invoke(FingerprintingSignalsProvider.kt:321)
       at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:74)
       at com.fingerprintjs.android.fingerprint.fingerprinting_signals.FingerprintingSignalsProvider.getTimezoneSignal(FingerprintingSignalsProvider.kt:321)
       at com.fingerprintjs.android.fingerprint.tools.FingerprintingLegacySchemeSupportExtensions$getDeviceStateSignals$43.invoke(FingerprintingLegacySchemeSupportExtensions.kt:177)
       at com.fingerprintjs.android.fingerprint.tools.FingerprintingLegacySchemeSupportExtensions$getDeviceStateSignals$43.invoke(FingerprintingLegacySchemeSupportExtensions.kt:177)
       at com.fingerprintjs.android.fingerprint.tools.FingerprintingLegacySchemeSupportExtensions.createSignalIfNeeded(FingerprintingLegacySchemeSupportExtensions.kt:20)
       at com.fingerprintjs.android.fingerprint.tools.FingerprintingLegacySchemeSupportExtensions.getDeviceStateSignals(FingerprintingLegacySchemeSupportExtensions.kt:182)
       at com.fingerprintjs.android.fingerprint.Fingerprinter.getFingerprint$lambda-7(Fingerprinter.kt:188)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
       at java.lang.Thread.run(Thread.java:764)

Most of them happened on the Android 8. Any insight about this?

Screen Shot 2023-06-21 at 13 52 35

Thank you

@Sergey-Makarov
Copy link
Contributor

Hey @fanjavaid!

Thanks for this report, we will look into that soon!

@Sergey-Makarov
Copy link
Contributor

@fanjavaid
Although it's surprising to get an exception from TimeZone.getDefault().displayName call, it surely must not cause the app to crash, so this is definitely a bug from our side.

I will prepare a release with a fix today, stay tuned.

@Sergey-Makarov
Copy link
Contributor

Issue was closed automatically. Reopening until we release a newer version

@Sergey-Makarov
Copy link
Contributor

@fanjavaid Release 2.0.2 is ready, the error you mentioned will not cause a crash anymore. Feel free to reopen the issue if you still have any problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants