I am using Xcode 7 and iOS 9. I'm having trouble in launching my app on my device using the new feature that Xcode 7 has, that allows us to try applications without having an Apple Developer Program
Here's what I get from Profile when I try to trust and verify apps. It keeps telling me that I need to connect to the internet but I'm always connected. I try to delete my profile and my app and restarting my phone but it doesn't work.
Any suggestions?
Error1
Error2
I'm currently having this problem right now too, Cellular, and quitting Settings didn't help.
This article (https://support.apple.com/en-ca/HT204460) mentions you need to be able to connect to http://ppq.apple.com to verify the app. As of right now (Dec 4th, 2015), it seems to be down.
"An Internet connection is required to verify the app developer's certificate when establishing trust. If you're behind a firewall, make sure it's configured to allow connections to https://ppq.apple.com. If you aren't connected to the Internet when you trust an app, the device displays "Not Verified" instead. In order to use the app, you need to connect to the Internet, and tap the Verify App button."
So I assume if that site is down, you can't trust apps.
I had the same issue. I tried to switch between WIFI and Cellular data but no results. I was testing on iPad Pro with ios 9.3.2 and I even updated it to the latest software update available which is 9.3.3.
Again the efforts were in vain! I still got the error message "No Internet Connection Error".
Then I noticed my Timezone and DataTime was different and when I set it to "Set Automatically", VOILA ! Afterwards, I could trust the developer and verify app successfully.
So make sure, you set the DATE TIME and TIMEZONE correctly while you trust a developer and verify apps.
Something has changed in the last day. Not sure if it's a Apple verification server issue or WiFi issue with iOS 9.0.2.
Anyway, the workaround is this. We have clients doing this today.
Disconnect from WiFi and connect via cellular. You may have to hotspot to a phone if your iPad is WiFi only.
Clear the Settings iOS app out of memory.
Re-launch the Settings app and go to Profiles.
Click Verify link again and should verify / work.
This worked for me. Stop debugging. Close Settings app (double tap on home and swipe up). Open Settings app again and got to General>Device Management>Select the app certificate> trust. This works
this happens when the phone has no wifi or 3G/4G signal. You may have run out of minutes on your data plan for example or disabled your wifi etc.
For me, the problem was that I was using a VPN (Charles proxy) and I forgot about it. Just turned off the VPN, accepted the profile, and switch the VPN on.
As of iOS 13.1.3, this now seems to be the message received when your distribution certificate is revoked. It used to just appear to force quit the app, but now it displays this message and refuses to verify. Rebuilding the app with a current certificate should fix it in this case.
Related
I have added a customize Framework to my project but when I ran the project the screen turn in black and got following error
log:
"unable to determine interface type without an established connection" & " unable to determine fallback status without a connection"
Its because as a safe connection could not be established may be because of security permissions or low internet quality.
Turn off your testing iPhone device and switch it ON again
If developer access is required for the project.
In the developer access section of the account used to develop the app on Xcode remove the iPhone for giving developer access on the device.
Connect the iPhone again and trust the computer. If any other apple device is active at the time with same account as used in iPhone, trust the macbook from those devices too. Finally give developer access if asked
Build the code again.
I needed to run a long test to see what's making my app crash. So I set the Mac to not sleep and I ran the app on the iPhone connected via USB overnight. In the morning, I found that the iPhone had disconnected during the night.
I looked for in Console and Xcode for device logs and I found there were none at all on the phone, therefore no history of what happened during the night. Logs began after the moment I reconnected the phone to the Mac.
I downloaded the app container and found no useful evidence of what happened.
iOS is 12.4 and Xcode is 10.3.
What can be done to ensure there is some evidence of what caused the crash? Other than filling the app with fprintf's going to a custom log file. Also I am using Fabric.
Do the same thing again, but this time with a camera looking at the PC. Maybe you can grab some evidence from the recording next day. Modern solutions for modern problems.
Go to Settings -> Touch ID and Passcode
Check if USB Accessories has been turned off. Your device may have disconnected then failed to reconnect due to this feature restricting access to the device if it is disconnected for more than an hour.
Change this setting, replace your cable or use a different USB port then try running it again.
I'm using Xcode 10.1, and I don't have a checkbox whether I want to connect through network or not on my device page (which was there in Xcode 9 and Xcode 10 beta). Search "connect via network xcode" on google images if you don't know what I mean.
However, I must debug the offline flow of my app (which is written in React-Native btw). Not just no-internet-connection, but turning off wifi and mobile-data, which will trigger a status change. By using the developer settings of the iPhone, I can make every call fail (100% loss), but cannot change the internet-status of the phone.
So I want the debugger to stay connected and either be able to:
debug the old-school way through the cable (if I turn off internet now, I get a red error screen and nothing is possible anymore), so I can disable wifi and mobile-data,
or simulating that status change on the phone.
Btw, I cannot use a simulator, since the app requires Bluetooth.
Thanks in advance!
Edit:
The checkbox is not there for older iPhone devices. With iPhone 7s, I do see the checkbox "connect via network". But enabling or disabling does not change the fact that your iPhone needs internet to debug. If I disable internet on the phone I get the following error:
Ok, I've found the problem. We are testing on a iPhone5, which is no longer officially supported by Apple. Which means that Apple has decided to cut features for iPhone5 so you would buy a new one (wonderful strategy =/). Hence debugging with a cable is no longer supported on iPhone5.
We tested with a iPhone6 from a colleague, and everything works fine.
Edit:
Altough the checkbox is there, and I can disable wifi for connection... The moment I turn off internet on the phone, the app crashes and says: "Runtime is not ready for debugging: make sure packager runtime is running"... so no solution yet...
I can trust app developers but I can't verify the apps. I need a quick answer please as I'm going away tomorrow. Here is the error I get:
1.Your network connection is bad，go to Apple developer in safari to check if network is ok.
2.Connect to another wifi or restart iPad
Yesterday, I submitted my app for review, but I got this message from Apple:
We discovered one or more bugs in your app when reviewed on iPad iPhone running iOS 9.3.2 on Wi-Fi connected to an IPv6 network.
Specifically, upon review we have found the application still experiences a loading issue and unable to review the application content.
My app uses ionic framework, how can I fix this problem?
I already used domain to access my server, but this problem still exists.
Yes. According to apple's policy , your application must supports IPV6. so, please check your application supports IPV6. Supporting IPv6 in iOS 9
To test, if your application supports IPV6 or not please check this ,
Supporting IPv6 DNS64/NAT64 Networks
To check with creating follow this steps , which indicate on apple's page .
To set up a local IPv6 Wi-Fi network using your Mac
1) Make sure your Mac is connected to the Internet(with ethernet), but not through Wi-Fi.
2) Launch System Preferences from your Dock, LaunchPad, or the Apple menu.
3) Press the Option key and click Sharing. Don’t release the Option key yet. (don't forget to press option key)
4)Select Internet Sharing in the list of sharing services.
5)Release the Option key.
6)Select the Create NAT64 Network checkbox.
7)Choose the network interface that provides your Internet connection, such as Thunderbolt Ethernet or Only Ethernet.
8)Select the Wi-Fi checkbox.
9)Click Wi-Fi Options, and configure the network name and security options for your network.
10) Select the Internet Sharing checkbox to enable your local network.
11)When prompted to confirm you want to begin sharing, click Start
12) Now your mac mini is working as a hotspot and useing IPv6 NAT64 network
(looks like above image when hotspot created)
Now connect your iphone with your mac mini's hotspot. and Test your Application it's working properly or not.
I hope this answer is helpful you.
Edit :- Don't forget to add below frameworks.
1) WebKit
2) CFNetwork
You will find all the information on this link related to ipv6 policy. Supporting IPv6 DNS64/NAT64 Networks
We also faced the same issue.
Just registered your website with any CDN like cloudFlare and your app will be approved next time no need to shift the whole site to any other server. This is the easiest way to get approval from app store.
I think Apple has something wrong with this error!
I have an app (ionic app) rejected 3 times (during Nov 2016) for the same error and lastly accepted without making any change related to IPv6!
You may need to check your app for startup errors if you think that you have nothing to do with IPv6.
By the way: I did not check IPv6 compatibility on my app, and even more the app - in its inner views - has a connection to a webpage that hosted on a shared host with no IPv6 support!!
Please note that sometimes the mobile app works in the test environment but not in the Apple own test environment. Following this and this link can be very helpful in determining what's the problem with apple rejections.
It is clearly stated that the test environment is not exactly the same