I've stored user settings in the SharedPreferences in my App, when I update the App via Google Play Store to a new version of the App data getting lost.
but if i store user settings in the SharedPreferences and then run google backup and then update the app via google play data getting restord and user setting updated in UI
any idea why its only working if i do auto backup?
Related
I'm building chat app for iOS using Xamarin.
My user starts with the browser version of my chat (using their favorite browser) and then can decide to download my app and continue from there.
My question -
On the web, I create cookie with userID. I need to pass the userID to the app to keep the user in context. How can I do it?
Thanks,
I'm trying to figure out where users of my app lose interest during the onboarding process. To that end, I've implemented Firebase Analytics. However, it seems that in the scenario where the user only uses the app once never to open it again, the collated analytics data are never uploaded to Firebase. Only when the app is launched a second time, the data are being uploaded.
Does Firebase Analytics have a means of forcing the uploaded upon app backgrounding?
There is no way to force the Firebase Analytics client to send its data to the server at any specific time.
But as Todd says in his blog post How Long Does it Take for My Firebase Analytics Data to Show Up?:
On iOS devices, Firebase will also send down data when your app moves into the background. So if a user tries your app for 20 minutes and then uninstalls it, that session data will still be received, because your app will have sent down the data the moment the user moved your app to the background.
The only caveat to this:
The one corner case where analytics data would actually get lost on iOS would be if your app crashed and then your user immediately uninstalled it.
So it looks like the analytics data should be sent to the server if the user background the app. If that doesn't happen for you, can you describe the flow of your users whose data is not showing up more explicitly?
In an iOS app, developed using Firebase Database, can a user make changes to database on his/her device that is reflected only locally on his/her device?
My app is a contacts app and I want any user be able to edit or favourite a contact which should be only reflected on his/her device and not to every user using the app.
I'd recommend reading up on structuring data in Firebase: https://firebase.google.com/docs/database/ios/structure-data
(When you're done, read all the docs or perhaps follow some video tutorials on Firebase.)
This will help you establish a better understanding of how Firebase works, helping you with more than just the problem at hand.
I built an app using Firebase, and I have persistenceEnabled turned on for caching data and auth sessions, etc.
I have a user who, every time he opens the app, it tries to login and load using the saved auth session, but his account was deleted, so it crashes.
He tried deleting the app, turning off the phone, even doing a hard reset by holding down the power and home button at the same time. But every time he opens the app, it still crashes on trying to load the persisted session data.
Is there any way to clear this data out short of restoring the phone back to its factory default settings or releasing a new version of the app?
Unfortunately, Firebase stores account credentials in the keychain and there appears to be no way for the end user to remove them (see this other question).
(If you're looking for a way to programmatically remove them, you should be able to call [ref unauth] or similar and Firebase will clear them.)
I want to implement a SharedPreferences kind of thing in my BlackBerry application similar to what is available in Android. What i want to do is store the login details after authenticating them so that the user is not required to login again and again.
Use PersistentStore class from RIM SDK to store data and share it among different applications when necessary.
You can use both PersistenStore and RuntimeStore to save data over the BB device. The main difference is that the persistent store will save your data even after a phone reset. But the runtime store will erase them after resetting the device. You can use the one that you see better for usage