I'm trying to use the Firebase Storage for images in my app. What happened was I wanted to change the name of my app as I've changed my mind on what the name will be, and so respectfully I updated the Firebase Console Project.
Corresponding name spaces were updated. After the rename of the app project I wasn't able to download the google.json file anymore. Even after deleting the entire project, and starting from scratch the google.json just wouldn't download kept saying there was a problem with the server.
There is another question with this inquiry, but it didn't have a single issue after upgrading to the new Firebase, and the question that is regarding this is specifically about having been upgraded . It took some learning, and there still isn't as much documentation as I'd like. For example, the FirebaseUI (ListAdapter) and such. Would solve a lot of my current issues in regards to handling data being moved, updated, deleted, etc.
Is there any way to know if this specific bug issue has been reported? Is it a known issue, and is there a possible timeline? I plan to scale the app once I launch and am afraid to do so as once I do. I will be upgrading the plan to the $25 plan for better simultaneous connections.
Any help would be graciously appreciated.
UPDATE
Since a few days ago I was able to download the google.json file. That is great! However, the issue still remains. I cannot use the Storage, and it's giving the same error as the attached image.
Also, I have submitted a ticket with Firebase Support. Communicating with Firebase Support currently via email. Will post updates as I have them.
Related
My app is written on android native code and I got this warning on the play store console
Your app "appName" version code "xxxx" includes SDK com.segment.analytics.android:analytics or an SDK that one of your libraries depends on, which collects personal or sensitive data that includes but may not be limited to Advertising ID, Android ID identifiers. Persistent device identifiers may not be linked to other personal and sensitive user data or resettable device identifiers as described in the User Data policy.
ACTION REQUIRED: Upload a new compliant version AND deactivate the noncompliant version.
But I don't have that library on my project, the only libraries related to firebase that I have are these:
"com.google.firebase:firebase-crashlytics:17.4.0",
"com.google.firebase:firebase-analytics:18.0.2",
"com.google.firebase:firebase-perf:20.0.2",
"com.google.firebase:firebase-core:18.0.0",
"com.google.firebase:firebase-auth:20.0.1",
"com.google.firebase:firebase-messaging:21.0.1",
But I don't know how to solve this, should I update all of them and upload my app again and check if I received this warning again or not to see if it was solved? I need to solve this because I won't be able to upload more app versions in the following months.
Thank you for being so helpful, it's really appreciated.
Some people have asked me if I solved this, and the short answer is yes, I did. Unfortunately, nobody gave me a specific answer about how to solve it, and the problem is that I think I used a bazooka to kill a fly.
The process for solving this was this:
I updated all Firebase dependencies, I was using these:
com.google.firebase:firebase-crashlytics,
com.google.firebase:firebase-analytics,
com.google.firebase:firebase-perf,
com.google.firebase:firebase-core,
com.google.firebase:firebase-auth,
com.google.firebase:firebase-messaging
I update them using firebase-bom version 30.3.2
Also, I updated other google dependencies, I'm not 100% sure that this affected the solution, however, I want to document all just in case you are also using them, and you can consider it out.
com.google.android.gms:play-services-auth:20.2.0,
com.google.android.gms:play-services-auth-api-phone:18.0.1,
com.google.android.gms:play-services-analytics:18.0.1,
com.google.android.gms:play-services-base:18.1.0,
com.google.android.gms:play-services-location:20.0.0,
com.google.android.gms:play-services-maps:18.0.1
After using these versions, I uploaded the new build and did not see the problem again in the Google console for this version and later
Sorry for not being specific in the needed dependency to be updated, I didn't have a chance to test the combinations to discover them.
I know that there have been a few posts linked to this issue, but I was unable to find one that solves my issue. Many posts have mentioned needing 3 keys in order to use Google login for Firebase, but for the past year, my personal project has done fine with just 1 key, the debug key. I have never generated an APK nor published to Google Play, hence I do not think that the other keys are necessary. All I want to do is to be able to log in to the application on my emulator using a gmail account. Normal email authentication works, as well as other firebase database and storage services, so I'm especially confused.
A couple weeks ago I renamed many of the directories in the project. I'm not sure if it is a coincidence or not, but checking the git logs, the authentication works before the renaming but does not after the renaming. This meant that I edited the google-services.json file, which is now different from from the one that I download from the firebase console. Could this be the reason? It's several commits and hours of work behind the current head though.
I have verified my fingerprint SHA1 on the firebase console with the one on Android Studio. They are identical. I'm not sure what else I need to do. Any help would be really appreciated. Thank you
Edit: I should also add that I saw a youtube video that just deleted the firebase project and restarted. That is a true nuclear option that I do not wish to do...
This is my first questions on SO, but I would first like to thank the community for helping me along the way in creating a few Android apps. I am not a programmer by profession, and most of the stuff I make is just for fun, but one Android app is a real project that I created for a client, and I've run into some real trouble and need some help.
The app I made basically takes in some data, stores it into an SQL database, and when necessary, uses queries to pull various information from the DB, and displays it. If any adjustments need to be made, I make them and just send them another .apk. No problem, until now...
I recently upgraded to Windows 10, doubled my laptop's RAM and replaced my hard drive with an SSD, and did a refresh of the OS. Everything, including Android Studio, runs like a dream now!!! I had a request from my client to make a few adjustments, so I recopied my backed up source code to my projects folder, opened the code, made the modifications, and resent the .apk to my client. They are getting the following message:
"X App not installed.
An existing package by the same name with a conflicting signature is already installed."
The only changes I made to the app were adding a table to the database (and upgrading the DB version number, of course), and modified some layouts and a couple of methods and calculations, etc. Nothing more. I have searched up and down and have even replicated the same error on my tablet and can't find a way around it. My client currently has a few months worth of data input into the app, so they can't just uninstall it and do a new app installation. Is there anything I can do at this point? Also, I never made any custom key signature, just programmed, made .apk, and have sent numerous updates without issue. Any help would be greatly appreciated. (I have all my project folders and .apks backed up for all the different versions that I have sent)
Thank you!
Your best bet at this point, assuming you can't find/get the original key, is to use a backup program (or adb pull worst case) to backup his /data/data/ folder. Then you can uninstall the original app and reinstall the new version. Then you can restore/adb push the old folder's contents to the phone to restore the data files. This may require rooting it.
If possible I would test this on another phone first, to make sure it works, since you only get 1 shot at this. I would also save your key in your source control repo in the future.
I did a major rewrite of my application to support fragment. I also took this opportunity to rewrite a bunch of code to make it more stable, cleaner, more maintainable, etc.
We pushed the new version on the Play Store. Unfortunately, some users complained that they had to clear the cache and the application data for the new version to work. Unfortunately, I don't have more information (as I can't contact these users). Clearing the cache and the data seems to fix the problem. I have no idea if the problem is that the app crash at startup. Or if the app start, but then is stuck in a endless loop.
We use Bugsense to have automatic bug reports. I've looked at them, but I can't seem to find the cause of the problem.
I'm curious as to what is stored and where. My app uses the "context.getExternalCacheDir()" to store images downloaded from the web. I store data in preference files, as well as in the SQL database. Before releasing the app, we had an internal QA to make sure the app upgrade was working perfectly. And most of our users don't have this problem.
What can I do to try to pinpoint the cause of this issue?
i have an app in the android market that utilizes the database as well as the shared preference .I need to update my application to add more functionality and new tables
I have updated the database portion in the upgrade() method of the helper class.
Please help in explaining the process of android application update.what happens behind the scene.How is application updated after we submit the updated apk in market
What all more thing need to be taken care apart from database
Please help it is urgent
During Google IO 2012 about 2 Weeks ago they presented a new way of updating the Android Apk from the Play store. So basically you just download everything whats new and add it to the apk which is already available. So now it will take upto 70% less data for upgrading an apk. So Your database will be updated. Just the new data will be downloaded and will be added to the app. The shared prefrences dont get deleted, they stay saved even after an update. I hope I could help.