Framework: Flutter
SDK: single_factor_auth_flutter version 7.0.1 (latest version)
Network: sapphire_mainnet
We are having a number of issues with single_factor_auth_flutter SDK version 7.0.1 (latest version) on our live app. Previously I had reported the PlatformException- lateinit property singleFactorAuth has not been initialized issue but this problem is still happening after updating the proguard-rules.pro file with. Here is the complete content of the proguard-rules.pro file
-keepclassmembers class com.web3auth.single_factor_auth_flutter.* {
<fields>;
<init>();
<methods>;
}
-keep class com.web3auth.singlefactorauth.** { *; }
-keep class com.web3auth.singlefactorauth.types.** { *; }
-keep class com.web3auth.singlefactorauth.** { *; }
-keep class com.web3auth.singlefactorauth.types.** { *; }
# Keep Gson serialized classes (prevents issues with reflection-based deserialization)
-keep class com.google.gson.** { *; }
-keepattributes *Annotation*
-keep class org.torusresearch.fetchnodedetails.types.** { *; }
-keepclassmembers enum * { *; }
# Keep the j2objc annotations that Guava needs
-dontwarn com.google.j2objc.annotations.RetainedWith
The PlatformException(error, null, null, null) issue is followed by the PlatformException(error, lateinit property singleFactorAuth has not been initialized, null issue and we have noticed that the issues resolve when the user clears the app data and app cache after they encountered the issue initially but this is breaking the user experience. Would love to know why this is happening and how to resolve this totally so it does not happen in the first place
Also another issue we encounter frequently on our live app is PlatformException(error, public nonce is missing, public nonce is missing, null) Our crashlytics service has been recording this more frequently and this is usually happening for our new users. We do not understand what may be leading to this issue and would love to know how to move forward with potential fixes for the issue
