Run App in the iOS Simulator
Go through the login flow and login
Stop App and Remove App from the iOS Simulator
Run App and notice that the cache persists; FirAuth.auth()?.currentUser is the user that I previously logged in with before removing the app.
My assumption that by removing the app from the simulator enables me to start from a blank slate next time I run is not correct.
Can somebody please explain how/why the cache persists?
Firebase manages this internally. The user which you get from FirAuth.auth()?.currentUser has nothing to deal with cache. So, even you delete the app from your simulator you will get currentUser.
Related
My Flutter app that has a login page is fully functional on Android, iPhone and Web.
The problem is with the WebApp - immediately after I deploy it into the Firebase, it works well, as expected. However, if I leave it and come back to it in several hours, and try to open another window - neither text fields nor mouse user entry are accepted any longer. If I then rebuild the app and redeploy it, it starts working, for a while.
I use flutter version 2.10.5 and Dart version 2.16.2.
Flutter doctor -v produced no errors or warnings.
Has anyone experienced this sort of behaviour?
I have a XF app already published on the play store and now I am targetting iOS. During developpent I made sure the app was still working on iOS, using the simulator only.
On the simulator everything works as expected, the launch screen is shown then the MainPage starts. But when I debug on an actual IPhone device, the app get stuck on the Launchscreen.storyboard for about 20 sec then the app exits. I've no debug output and it seems that the AppDelegate is never hit. Breakpoints in AppDelegate.FinishedLaunching method are not hit for instance. I tried to F11 for start in debugging mode but I don't hit anything, still hanging on the launch screen. I was expecting the transition from simulator to device to be less painful.
My plist file contains the following permission requirements
...
<key>NSLocationAlwaysUsageDescription</key>
<string>We need to use your location</string>
<key>NSLocationWhenInUseUsageDescription</key>
<string>We are using your location</string>
<key>NSPhotoLibraryUsageDescription</key>
<string>This app needs access to photos.</string>
<key>NSPhotoLibraryAddUsageDescription</key>
<string>This app needs access to the photo gallery.</string>
The only difference I saw is that location permissions are not asked on the device while in the simulator it asks for it at start. But this might be related to the fact that I can't reach AppDelegate, I am not sure yet.
The iOS project was generated via Prism templates. I am using VS 16.8.0 on Windows, XF 4.8.0.1687, Prism 8.0.0.1909, Xamarin iOS SDK 14.4.1.3 and I am set to "don't link" for linkers option. The device is an Iphone 10.
Any idea how can I find out the root cause - or get some useful logs?
Thanks in advance for your help.
EDIT:
Here are the device log output during a new installation https://taits.s3-eu-west-1.amazonaws.com/devicelogs.txt. I am trying to go through them but kinda lost.
I wanted to run my swiftui app on macos, unfortunately i can still see error That
Running InstanceID on a simulator doesn't have APNS. Use prod
profile by default.
I used the code from firebase messaging docs to initialize firebase messaging and later on I wanted to get instance id token.
While using Xcode I don't get any other errors instead of this which I mentioned. That's why I decided to archive my app and run it independently
outside Xcode. Unfortunately I still can see in console error message about running in simulator. When I run that code on my physical iPhone everything works properly.
Xcode log
Mac console log
Does anyone know what should I change or how should I archive the app properly in order to firebase not detect my app as simulator?
I tried to load my App to iTunesConnect today but I got an error during the build re. no provisioning profile found (when I run it just for my iPhone App it works just fine and has been fine for a while now). So I assume this is because I have added a Watchkit App.
How do I resolve this ?
Do I need to create a new App in iTunesConnect for the Watchkit app ?
Thanks.
You don't need to create a new app for your watch app. It's a part of your main app as an extension.
You could resolve your problem by just signing out from the account settings in Xcode and then signing in again. Worked for me.
First of all click onto the accounts tab.
Then select your Apple-ID and click minus.
Then click onto the plus button and add your Apple-ID once again.
I am working on a simple mobile web app and I am having trouble logging in...
I followed this little sample on making a custom login: http://blog.benmcmahen.com/post/41741539120/building-a-customized-accounts-ui-for-meteor
Nothing too tricky here.
So I run my meteor server locally. On my computer, through the browser, I can log in and create accounts -- no problem.
When I go to my local IP from my iPhone, the website successfully loads but for some reason I am not able to login or create accounts.
I have noticed that for Meteor.loginWithPassword and Meteor.createUser, the callback function NEVER gets called. I have {{loggingIn}} rendering a loading screen and the loading screen is only there for a fraction of a second before the form is reloaded. No errors are thrown (validation passes and the callback function doesnt fail).
Out of suspicion, I deployed the app and tried accessing the deployed website from my phone and the same issue persists...
Any ideas what I cannot log in or create accounts on my iPhone, but I can on my computer? Maybe its a cookies thing? Any ways of solving this?
Thanks a lot,
Chet
Edit:
This works on both my desktop browser and iPhone simulator. Just not my iPhone. Could it just be a local network issue? -- No, even if I deploy the website, I have the same issues...
Also, check out my github post about recreating the issue:
https://github.com/ccorcos/meteorPasswordMobileError
Check to make sure that you are running the same version of iOS on all the devices you are testing on. I have seen iOS 7 misbehave when using Meteor apps. iOS 6 works just fine.