There's a bug in this app I'm working on that was made using the Ionic Native Google Maps API. When I run it on an iPad (simulator or actual device), the map API fails to load, but only when run the first time. On all subsequent loads of the app, it works without any issues. IIRC, the app will hang when loading on an iPad below a certain iOS version.
This bug does not occur on iPhones or any Android devices, and I do have the proper API keys in the app's config.xml. My only clue to the issue comes from an error message that appeared when I used Safari's Developer interface to inspect the app (certain things redacted for privacy concerns):
CoreData: annotation: Failed to load optimized model at path '/Users/(user-name-redacted)/Library/Developer/CoreSimulator/Devices/EBF1B0A1-87A8-4E14-8C05-73AF1CB05F05/data/Containers/Bundle/Application/5358FE37-CECB-481D-BCFE-ECA309540DE4/(app-name-redacted).app/GoogleMaps.bundle/GMSCacheStorage.momd/StorageWithTileVersionID.omo'
Again, this error message only appears on an iPad when the app is being run for the first time after installation. But most users are going to assume an app isn't going to work at all if it doesn't work properly the first time.
If anyone could provide any insight to what's going on and how to fix this, I'd appreciate it. This one issue is keeping my company from putting this app in the Apple Store.
Related
I'm new to iOS development.
I have a app built with React Native and already deployed on app store. I'm working on version 2.0 of the app. Previous version was built by some other developer company.
They delivered the source code for the version one, I'm gonna work on top of the codes of version one.
I've pushed a build on TestFlight to check if the existing codes are okay.
Now on TestFlight,
most of the testers are not finding any problems but some users can't login. Whenever they try to login, either there is an infinite loading screen or the app takes back to splash screen. The users then tries again to login but again after entering otp, user is sent back to splash screen.
Now this scenario is happening only with 2, out of our 20+ testers. We don't know where the problem is because we can't recreate the same issue in other devices.
Also, this same app with same code is deployed on google play store and working without any issue.
Has anyone else faced similar issue? Is it a problem with the test flight?
N.B: Everyone using iphone with latest iOS update 16.3
Try to log in with their credentials on your simulator/local device where you have access to logs etc.
Sounds to me like there's an issue with some specific accounts, maybe they have some properties in their accounts that has been altered/removed that's making the login process fail / load the correct content.
Edit: If there's infinite loading, have they checked their internet connectivity as well?
I’m experiencing with issue when trying to clear my app data to start a new test class. When using an Android driver, resetApp() works just fine, but for iOS it just seems to close the app and launch it again, without actually clearing the data. Here, I can’t use removeApp() because the device, it does not allow me to install the app.
Could you please guide me? Execution is effecting to daily run through Jenkins.
Earlier I was using UIWebViewEngine in my ionic 3 projects but this was resulting in slow scrolling of list in iOS devices. After going through http://jayantpaliwal.com/2017/07/tips-for-ionic-app-to-perform-better-in-ios/ I changed UIWebViewEngine to WkWebViewEngine, my scrolling issue got fixed, but now a new issue has raised. When performing a PUT request from an iOS device my server is giving "Method PUT is not allowed by access-control-allow-methods" but this is working fine in android device.
When I roll back to UIWebViewEngine, it is working fine but scrolling issue raised again.
Please suggest your solutions. Do we have do configuration in backed OR frontend
I started messing around with react-native. I've built a small application and it seems to work fine (package.json). I can work on it in Debug or Release mode, using the simulator or my iPhone 6S device, and all is well.
This app is just for me so I don't pay for the Apple Developer thing, and I just run the app in Release mode on my device, and it...seems to be fine? I can quit xcode and go places and the app works fine.
After a week or so, it's hard to tell, the app stops loading. It'll display the splash screen for a split second and then it's gone back to the home screen.
I setup Rollbar, but it doesn't catch anything. I look in the Privacy -> Analytics area and don't see anything there either.
I'm not really looking for an answer to my exact problem since various SO questions and other places suggest it's probably something weird and specific. My main problem is I don't know even where to look/how to debug this kind of thing. If I build the app and run it on device again, it'll run fine. I need to try to debug without loading new code, and have no idea how that works on iOS. I've tried poking around at the Debug -> Attach to Process by Name, but the app never gets far enough to do anything with that.
Alternatively, I throw react-native in the garbage and use something that works...
App provisioning with a free developer license (?) is 7 days. See: Why does my free XCode Provisioning Profile only last 7 days?
You can likely verify this by looking at error messages in the console window. Connect your device, and in Xcode go to Window/Devices and Simulators/Open Console, then launch your app.
I've got an app that uses Core Data that sporadically stops launching so I have to reinstall it using XCode and then it launches again like normal for a while, with all the Core Data information still preserved.
I have seen that an app often stops launching when the target of an app is too low in comparison to the device software version, however this is not so for this app and device (iPhone 6s).
Have you had such an issue before? What do you think could be causing this problem?
There are many, many, many things that could cause an app to fail to launch. You need to narrow things down and collect some data so that you can find out what the problem is and do something about it. Right now you don't even know that it's related to Core Data, you're just guessing.
For a crash on launch, look at the device console and see what messages appear when you try to launch the app and it fails. You can get the device console messages by
Connecting your device to your Mac
Opening Xcode's "Devices" window (cmd-shift-2)
Looking in the bottom half of the window
A better way to watch the console is to use the free iOS Console app.
The problem was that, as mentioned by dan in the comments, the code was being signed for a short period of time (7 days) and so I had to keep re-installing it on the iOS device to keep it working. Thus to keep the app working indefinitely a paid developer account is needed.
Also mentioned in this reddit forum:
https://www.reddit.com/r/jailbreak/comments/4hotx3/news_free_developer_account_installs_reduced_to_7/