I install Phonegap on my system and on my android phone.But when I want to connect to app by my mobile , app stay in downloading...
*I checked my ip and port and there are correct.
How i can solve this problem?
i find the problem. my firewall was active and dont allow to connect.
for solve you should right click on Anti-virus and disable firewall.
Related
As the title suggests the app is not opening up without internet because it needs to verify the developer (which is me). I also cant open it after killing the application without running it from my mac.
Is there any way to make this proccess smoother? I would like to be able to open application without reinstalling it everytime from my mac. I would also like to run the app without internet.
I need to be able to do this to test the offline mode on my application.
Appreciate any suggestions!
I have been working on a react native project in Windows 10 for a while now using Expo to scan the given QR code and test the app on my IOS device. The other day I ran $expo start and everything seemed to go fine until I tried to load the app on my IOS device. I received this message:
Could not connect to server
I then "Run in Web Browser" which worked fine, so I tried accessing 127.0.0.1:19000 in my Iphone's browser (firefox) and it as well could not connect to server. My phone is connected via wifi which is 2.4 or 5g. I wasn't sure how this would effect this so I used a wifi adapter on PC to match which wifi connection phone and PC were on and that didn't help.
I am using react version 17.0.1, expo version 3.28.5, and "react-native": "https://github.com/expo/react-native/archive/sdk-38.0.0.tar.gz"
I have tried:
Turning off windows firewall
Using different Iphones to connect
npm install --global expo-cli
Changing Connection from "LAN" to "Local"
Reinstalling Node
Creating a System Variable called: "REACT_NATIVE_PACKAGER_HOSTNAME" with the value "192.168.2.108". This did change the LAN IP address as intended but it did not resolve the problem. I just got the same message with the new IP address.
This problem just started happening out of the blue and I'm not really sure what to do next. If you need any additional information I'd be happy to give it.
try to use
expo start --tunnel
When you get the message:
"Error loading DevTools ValidationError: "urlType" must be one of [exp, http, redirect, no-protocol]"
Just wait for a bit and the QR code for tunnel will appear. It does the same for me as well.
Yesterday I started an Android Things project and I was testing the app using Android Studio. In order to connect to the device using adb.exe, I used the IP of the android device that I saw on the default OS's app (the starting screen). So, after the yesterday's testing it seems that my app is now the default app even if I don't have it connected to the PC.
The problem is that now I cannot see the device's IP address so I can connect to it using adb.exe.
Is there a way of going back to the default OS's app?
PS. The only solution I found is re-installing the Android Things OS.
To go back to default android thing logo screen.Uninstall the app using
adb uninstall <pkg name>
If you want to connect to AT without knowing ip use following command
adb connect Android.local
Also you can use serial cable to find ip of AT.
If you install multiple apps.AT will ask for your choice as below
uninstall the app using adb
adb uninstall <package-name>
if you have connected a keyboard to the raspberry pi board, you can go to the home screen by pressing escape button
(I don't have enough reputation to comment so I make an answer, sorry)
If you want to know the IP of your Raspeberry from your computer, you can use the ARP table.
From Ubuntu/Linux or Windows, just type arp -a
Your Android Things device will appear in this list with its IP !
If you don't need to uninstall your app, you can just close it:
adb shell am force-stop <package-name>
and of course you can close it from your app:
this.finish();
Also you can show your ip address in your app if you have screen. For me adb connect Android.local doesn't work.
An easy way is to log into your router and see all of the connected devices and pull the ip address from there. Really easy with Google Wifi
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
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.