Fabric Crashlytics Beta deploy fails: Project is inactive

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP


Fabric Crashlytics Beta deploy fails: Project is inactive



I am having a react-native app with the bundle com.name.dev.app. I added Fabric/Crashlytics to both iOS and Android and use Fabric Crashlytics Beta for internal distribution. I see both Apps in the Fabric dashboard and when building a release build I can see the crashes in the respective apps's dashboard. This worked for about 7 days.



Now, when trying to upload an APK to Beta via the Android Studio Fabric Plugin or via our Fastlane CI Pipeline, I am getting an error saying:


WARN - Crashlytics had a problem uploading the distribution. Project applicationname is inactive
Exception in thread "main" com.crashlytics.tools.android.exception.PluginException: Distribution upload failed.
at com.crashlytics.tools.android.DeveloperTools.processProperties(DeveloperTools.java:667)
at com.crashlytics.tools.android.DeveloperTools.processArgsInternal(DeveloperTools.java:348)
at com.crashlytics.tools.android.DeveloperTools.main(DeveloperTools.java:273)
Caused by: com.crashlytics.tools.android.exception.DistributionException: Crashlytics halted compilation because it had a problem uploading the distribution.Project applicationname is inactive
at com.crashlytics.tools.android.DistributionTasks.uploadDistribution(DistributionTasks.java:91)
at com.crashlytics.tools.android.DeveloperTools.processProperties(DeveloperTools.java:665)
... 2 more



I removed the Android app from Fabric and tried to recreate it. That failed, so I had to reach out to Crashlytics via Twitter and someone was so kind and manually re-activated the app again for Android. Crash collection still works on both platform and uploading new IPA files to the iOS is flawless. But I cannot upload an APK to the Android app.



I am a bit clueless. The project ist kind of active as it receives crashes but doesn't allow me to add APK to Beta.









By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.
-

Popular posts from this blog

Stripe::AuthenticationError No API key provided. Set your API key using “Stripe.api_key = ”

Image
Clash Royale CLAN TAG#URR8PPP Stripe::AuthenticationError No API key provided. Set your API key using “Stripe.api_key = <API-KEY>” UPDATE: I set the publishable key directly inline like so: Stripe.setPublishableKey("pk_live_*****"); and it works!! The problem is it is not properly configuring with ENV['stripe_publishable_key'] . Stripe.setPublishableKey("pk_live_*****"); ENV['stripe_publishable_key'] ORIGINAL POST: I am using the koudoku gem for Stripe. Everything works fine locally, but when I push to heroku, I am getting the error: Stripe::AuthenticationError (No API key provided. Set your API key using "Stripe.api_key = <API-KEY>". Stripe::AuthenticationError (No API key provided. Set your API key using "Stripe.api_key = <API-KEY>". Even though it sets the publishable key in development. Also, if I run heroku config, I see the keys there. What is happening here? Why is it not setting the key?? application.yml
Read more

CRM reporting Extension - SSRS instance is blank

Image
Clash Royale CLAN TAG#URR8PPP CRM reporting Extension - SSRS instance is blank Trying to install Reporting Extension for CRM 2016 but SSRS instance is blank. VM containing (SQL & CRM on the same machine ) Can you please help me how to fix the error below (SSRS instance name is empty). Can we install reporting extension on SQL server 2017 (should be OK as I was able to install CRM server)? By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.
Read more

Keycloak server returning user_not_found error when user is already imported with LDAP

Keycloak server returning user_not_found error when user is already imported with LDAP I am currently running a keycloak server as a service in a kubernetes cluster. I can access it perfectly with the initial keycloak admin account and used it to setup a new realm using LDAP for User Federation. The connection and queries seem to work fine as a I can search for Users and they pop up with their correct username, first name, last name and e-mail so all seemed fine. When I then log out and try to log in with a normal user account that exists in the AD and has been imported I just find get the following error: WARN [org.keycloak.events] (default task-8) type=LOGIN_ERROR, realmId=master, clientId=security-admin-console, userId=null, ipAddress=<my ip>, error=user_not_found, auth_method=openid-connect, auth_type=code, redirect_uri=http://myserver.com/auth/admin/master/console/#/realms/MyRealm, code_id=a8ca7f06-dfec-4e6e-8f6b-74eb871f71da, username=myUser So it seems that in some way wh
Read more