First app development in ReactNative. I just started to load data in via API and now the App crashes on my phone - but works fine in the simulator. The only errors I have (nothing in console) are from xCode, see image:
Any help debugging / fixing this issue?
Thanks
This was an issue because I was running 8.2 in simulator and 10.2 on my phone. 10.2 does not allow you to fetch using http, only https.
Related
I'm building a React Native which works fine when I run it on the simulator. However when I package it and put it on the Apple TestFlight, the app doesn't run on devices. All I see is a black screen.
I'm using the MongoDB Realm SDK if that may hold a clue to the problem. I'm fairly new to iOS development and only have the simulator to test the app.
Any ideas on how I can resolve this? Thank you!
Update: I tested the app on an iPod touch (iOS 14) and it works. So the problem seems occur only on iPhones.
This usually means that your app has crashed...Try using componentDidCatch and show an alert or something to get the error or try using sentry.io to catch crashes
My project works well on development mode.
It also works on release mode.
And even works well on TestFlight below iPhone 11.
It only crashed on iPhone 11 with TestFlight.
It crashes when I call my own rails API on AWS EC2 instance.
Has anyone ever been in this kind of error?
It also works well on iPhone 11 Pro on my local but only crashed on TestFlight.
I'm using Alamofire for my rails api call.
I finally solved it.
We can check TestFlight Bugs:
open Xcode
open menu Window/Organizer
select your project
there are 4 buttons on the top - Archives, Crashes, Energy, Metrics.
That it's.
You could check logs from Crashes.
Arrgghh....I am so fed up with Apple. I have none of the problems with Android that I continually have with Apple.
Went to go load my app onto a local device (iPhone 6s) that had iOS 10.1 on it. Xcode wouldn't play with that so I had to upgrade to Xcode 8.1 and everything broke. I am now just trying to deploy my project to the simulator, it builds fine and deploys - I see my splash screen and then the app goes blank. Zero errors are displayed in the console yet I am not able to see the app in Safari Develop "Simulator" (not even there).
Mac 10.11.6 El Capitan
Xcode 8.1 (8B62)
Cordova 6.4.0
Project platform iOS: 4.2.1 (I even upgraded it to 4.3.0 but still nothing, then rebuilt project with 4.2.1 again)
Project iOS Target: 9.3
Deployment Target: 9.3 (iPhone only)
Simulators: 10.0, 10.1, 9.3
It was deploying just fine to Simulator iPhone 6x with Xcode 8.0 for 9.3 deployments, but upgrading to Xcode 8.1 broke it. I am going to remove the Simulators 10.0/10.1. the biggest issue is it builds just fine but deploys splash screen then goes blank.
Relaunch Safari after Simulator starts running.
#eb1 gets credit for these 'fixes'.
After upgrading to Xcode 8.1 as well as Safari 10.0.1 I was no longer able to see compile, debug or JS errors in either the Xcode console or the Safari Develop Simulator debug/console sections.
After compiling my project, the simulator would show my app splash screen and then go blank. no errors, messages, console output - nothing. In addition, Safari was no longer displaying the "Develop -> Simulator" option to debug my app.
To fix this, I had to shut down Xcode and Safari, and in this order, relaunch Xcode, load the project into Xcode and then start Safari - only then would the Develop->Simulator dropdown show up.
But even after getting #1 to show up, I still wasn't able to see any bugs, or code issues within the Develop->Simulator window after the app had loaded. After it was loaded it would just be blank and i couldn't see what any issues that was causing my app to not be working. Well, after it was loaded i had to press "cmd-R" to reload the console/debug messages and then i was able to see the issues breaking my app. I have to do this every time now...load the app, see nothing, then cmd-R...then able to see the bugs/breaks.
I still don't have a solution for doing the same within Xcode console - prior to upgrading I could see almost all of the same issues in both Xcode and Safari, but now only in Safari (using solution #2 above). Xcode shows everything loaded fine, while Safari cmd-R 'after' loading is now showing the compile issues.
If anyone ever finds a solution for #3, please please add to this thread.
I'm trying to connect to bluetooth printers using a third party libraries. Everything works fine on iPad, iPhone, iPod touch. Now i have 3 iPad Air devices and I always got the following error message:
ERROR - sock can not connect: 2
On all other devices, the connection works fine. Any idea, what I can do?
Same problem:
https://discussions.apple.com/message/30117834#30117834
I don't have 50 rep so I can't comment on your post, sorry.
What version of iOS is on your iPads? There seem to be some external accessory connection issues in iOS 9.3.1. They should be fixed in 9.3.2. I've tested the beta and it seems to be working as expected again.
I reinstalled iOS 9.3.1 with a ipsw and it worked again.
I think there may be some configure files created before iOS 9.3.1 make this bug happen.
I had the same issue recently on an iPad 4 mini running iOS 11.0.3 trying to connect to a Socket Mobile scanner in MFi-SPP mode. The bluetooth connection seemed to work properly, but as soon as the Socket Mobile SDK tried to connect I also got the ERROR - sock can not connect: 2 errors.
I ended up doing a factory restore which resolved the issue, but I never figured out what was causing it.
I was getting the same error with Socket Mobile scanner, on iPad Pro with iOS 11.0.3. Updating iPad to latest iOS version (11.3) resolved the issue.
At the same time, on another iPad running on iOS 11.1, it was working fine.
I'm building an app and using alamofire to make web requests. When I attempt to make a request in iOS simulator 8.3 (any model) I get an NSURLErrorDomain code=-1005. YET, safari inside the simulator works just fine. My code and requests also work fine in all iOS 7.1 simulators. This is getting beyond frustrating for me to solve since restarting the simulator, resetting the content and settings and restarting xcode + computer has not solved the issue. Any ideas?