0
votes

Recently, i had to updated crashlytic dependency which requires firebase core dependency. this leads to a strange remote config failure on devices without google play services support (Huawei devices and emulators).

Exception happens when i try to fetch remote config values :

await remoteConfig.fetch(expiration: const Duration(hours: x)); 

Exception: Unable to complete fetch. Reason is unknown but this could be due to lack of connectivity.

when i revert back changes for firebase_core initialisation, that line goes through and remote config successfully fetched.

tried updated all related dependencies to the latest versions with no success:

firebase_core: ^0.5.0+1
firebase_remote_config: ^0.4.0+2

regarding to this post and documentation remote config should not depend on google play services and it should fetch without any problem , also as in some other threads mentioned about restricted api key i did not restrict firebase api key. any help and insight would be highly appreciated.

1
Does this work for you: stackoverflow.com/q/61513995/13329100shirley
thanks for sharing but latest update for remote config/ firebase core fixed the problemArash GM

1 Answers

1
votes

Firebase Remote config: Firebase did not rely on GMS at the beginning, but later versions used AAID of GMS, which led to dependency for GMS, but the new version in the 2nd half of this year cancelled the dependency on GMS, so currently the latest version does not depend on GMS.

Firebase Crashlytics: Depend on GMS. (tested on Huawei Mate 30 which doesn’t have GMS) The crash log and crash information can be uploaded, but because there is no GMS, it is impossible to count the crash rate and other information. Tested on Huawei Mate30 mobile phone(No Google GMS service), the crash log and related log events can be obtained, but there is no information such as the crash rate.