I am developing an iOS app with react native. When I run my app on a real iOS device via Xcode, code changes are not reflected anymore. It keeps building an old code version of my app. However, as soon as I run the app in the simulator, it uses the latest code. Unfortunately, cleaning the build folder, deleting ~/Library/Developer/Xcode/DerivedData/ and removing the old app from device did not help. Does anyone know a solution?
Related
I was working on an ionic 4 app. When I finished adjusting, build the app for iOS again on VS Code, I switch to XCode and start building to test on my iPhone device.
But sometimes the app wasn't updated. The app I run on the browser on my laptop is the updated version, but the one finished building on my iPhone is not the updated one. Even changing the identifier won't work. (But sometimes it gets updated)
These are the code I was using for rebuilding on VSCode. After running that, I switch to XCode, adjust the signing setting and run building on my iPhone. I am sure the cookies and other temporary storage are not being used in the new app as I would need to log in again every time I build, and I use a unique identifier in every build to prevent that.
ionic cordova platform remove ios &&
ionic cordova platform add ios &&
ionic cordova plugin add cordova-plugin-ionic-webview
If anyone has encountered something similar, please let me know how to fix it. Thanks.
currently I'm working on a flutter project and I'm new to it. The app is working fine on android device and iOS simulator. But when I try to run the app on iOS real device I'm getting issues. I tried in two ways,
I took a direct run build to a real device, and that time it is working and app is installed on my phone. But when I open the same app after disconnecting the connection between phone and Xcode, or when open after killing the direct run, it is simply opening the app and immediately closing. And showing no errors.
And I took an archive build, using diawi.com I convert .ipa file into a link, and when I try to install the app, after showing the animation of downloading and installing the app turns to a disable look(app icon changed to grey color) and when I open the app it says, cannot install the app.
I don't know why it is happening. I tried through Automatically and manually code signing style. But in both case I'm getting this issue. But when I run a simulator there is no issue. Please help me to fix this.
After installing 11.1 I created a new project, removed the multi-window stuff that Xcode now gives you by default, and started developing a test app that uses Vision Framework.
By the time I got to the point where I needed to test on the device instead of the simulator, I was struggling to make my app work correctly. I finally realized that running the app on my phone required me to delete the app and run a fresh install or the changes wouldn't be pushed to the device. This continues to be a problem. Even a new print statement won't be shown in the debugger output unless I go through the rigamarole of deleting the app and running fresh. Subsequent changes still use the initially installed build regardless of the number of times I clean/build/run.
I've cleaned the project, build folder, derived data, Xcode cache, rebooted my Mac, rebooted my phone, reinstalled Xcode, obliterated and reinstalled Xcode again, all with no success.
Anyone else with this issue? What am I missing?!
Ok, after two days of trying to fix this, it turns out to be some kind of Apple bug on iOS 13 (surprise, surprise).
Here's what I did/found:
I tried running on another device and was able to see changes on subsequent runs.
Back on the original test device, the issue still exists (Xcode issue ruled out)
I had a couple other test apps that were signed with the same development cert on the device, so I deleted those too.
Running the app from Xcode again prompted me to go to settings to trust the developer certificate
Changes and updates are now pushed to the device on each run from Xcode.
TLDR:
If you happen to run into a similar issue, try deleting other development certificate apps you have on your device and re-trust the certificate.
I test my app on the iOS simulator without a problem, on Android everything is fine, but when I download the app on the iPhone, it doesn't work. It gets stuck in the LaunchScreen and suddenly closes after about 10 seconds.
I have no clue why. I already tried a possible solution that was to specify the node version on the Build Phases > Bundle React Native code and images
App on Android already released but I'm facing this issue on iOS.
Debug
Same Wifi
No VPN on
Plug in your device via USB
How do you correctly use Application Data bundles in Xcode 6? I exported a .xcappdata file from a device, added it to my workspace, and selected it in the Run Options of a scheme.
Whenever I try to run the simulator with iOS 8.0, I get the following error, even on repeated launches, manual launches, etc:
Application data package not copied to the Simulator
It appears you are running 'REDACTED.app' on the iPad Air Simulator for
the first time, and therefore do not yet have a data folder created.
The application data package will be installed the next time you run
your app in the Simulator.
Trying to use the simulator with iOS 7.1 crashes Xcode.
Does this feature just not work anymore with the changes made to the filesystem?
Tried again on Xcode Version 6.1.1 (6A2008a) and it (sometimes) crashes Xcode now, hopefully that means it will be get fixed soon...
I'm using Xcode 8.1 and when I tried to add the .xcappdata file Xcode crashed.
I solved it by cleaning the app and then I tried to add it in another target and it worked. Afterwards I tried to put it again in the target I wanted it in and it worked as well.
Unfortunately I'm not sure about which of these steps fixed it but I hope it to be useful to someone!
You can try to clean the Derived Data which contains all the intermediate build information like debug- and release-built targets. And you probably can select the Simulator, choose the iOS Simulator from the menu. Then, choose Reset Content and Setting.
Sometimes, it's just some bugs in the XCode. And I think Apple is handling that when your issue is marked by duplicate by them.