I have encountered an odd problem the second time submitting an update to the app store.
I am building an app using Ionic Framework with a Java backend. Right now we use Firebase for user login.
We had a tough time getting our app onto the store this June because our server did not support ipv6 originally. After setting this up we got through review. But now that we are trying to submit an update (with a new reviewer) they cannot log into our app over ipv6 from a fresh install.
After further testing, we realized that our firebase url does not appear to be reachable over ipv6 (although we still haven't replicated the app review's report - our test correctly displays an error message, but they said that the app freezes).
I find it hard to believe firebase is not ipv6 enabled, but the testing indicates that that is the case. (once logged in ipv6 works fine with our server, we think firebase's capability to auto-relogin users offline is why we mistakenly made it into the store in the first place). Has anyone experienced similar issues with your firebase app? What did you do to resolve it? Did you end up having to abandon firebase or does the problem lie elsewhere?
p.s. I've looked long and hard but couldn't find any documentation about fireabse's compatibility with ipv6 or lack thereof. If anyone has seen this kind of documentation, that would also be immensely helpful.
Unfortunately Apple seems to miss-attribute any bug related to networking with IPv6-compatibility problems (as long as they hit it during compatibility testing). Most of the time, they aren't actually related to Firebase IPv6 compatibility.
Firebase has been tested on IPv6 and is compatible. You should test your app in an IPv6 environment, and check the stack trace of any error you find. If you see that Firebase is causing to the error, file a ticket with support.
Well, you could make some networking shinanigans like using an IPv6 reverse proxy that connects into your firebase via IPv4 which would lead them to be able to log in using IPv6, even though Firebase doesn't support it.
I suggest looking NGINX for that if you'd like to implement it yourself or looking into Cloudflare if you'd like to get that as a service.
Related
We have an app that registers and runs a NetworkExtension (specifically NEPacketTunnelProvider) on both iOS and macOS. This works fine (although not in the iOS simulator, of course, known limitation). However, when the network extension is running, the App Store on macOS/iOS, and TestFlight on iOS, fail to update the app. It looks like they're waiting for the NetworkExtension to terminate, but not actually asking the VPN to disconnect.
We don't want our users to have to think about killing our VPN (which should stay connected whenever possible), but we don't want them to have to think about updates either - they should happen automatically.
Are we missing something? Is there an event we should be listening on to detect that the store is trying to install an app update? Conditions when we should arrange for the VPN to terminate, safe in the knowledge that it will be restarted again after being updated?
Apple had bugs regarding this issue. It was supposed to be ok since iOS 11 (and macOS 10.13 or 10.14), but then users reported that the problem still exists. Several bugs regarding this are still probably open at Apple's bugs reports, but we can't check their status.
You can ask again at their forum, and open another bug regarding this issue.
Probably there's nothing else you can do.
Those are only some of the reports related to this issue:
https://forums.developer.apple.com/message/174708#174708
https://forums.developer.apple.com/thread/92603
https://forums.developer.apple.com/thread/126471
https://forums.developer.apple.com/message/149563#149563
https://forums.developer.apple.com/message/183927#183927
Edit: Someone just posted a question regarding this at Apple's forum. It might be you who posted to question, but maybe it's someone else, so there's another reference:
https://forums.developer.apple.com/thread/128894
My app has been rejected 4 times because of ipv6 incompatibility.But I have already made changes in my app to support ipv6.
1) I have used latest AFNetworking class
2) checking reachability with hostname method
3) Even made our server fully ipv6 supported.
Then also app gets rejected with following reason:
We discovered one or more bugs in your app when reviewed on iPhone running iOS 10.2.1 on Wi-Fi connected to an IPv6 network.
Specifically, launching your app, resolves to a black screen.
I had faced same issue. Mine was also rejected due to IPV6. Check below two things for your application:
1) Make sure you API link which you used in your application, doesn't have any ip address. If you calling API using IPAddress then your application will rejected.
2) Do testing your application using IPV6 network thorugh your system. Here is the link.
If your application is fullfill both testcase, then don't do any thing, just right comment in iTuneConnect and told them that my application is running in IPV6 network. Can you please guide to find my issue? If possible then can I have a call with your representative?
So they ask your contact detail and give you call and your issue will resvoled. I have wasted around 20 days to solved this issue. But apple representative told that this is them internal issue.
So my humble advice to contact Apple representative as soon as possible and your issue will resolve without doing anything.
I already have this issue with Apple guys, even with an IPV6 compatible app. Make sure the server you are calling is IPV6 compliant. You can use for example This site to test that the WS/server/machine you want to reach can "talk" with this protocol.
If it's the case, you can easily explain to Apple that the app is IPV6 compatible, by using URLSession only (for example), but it's the distant server which is not.
Got the problem twice, twice explain as above: succeed.
EDIT: Be sure by using AFNetworking, you are using 3.x version, and not 2.x (not IPV-6 compatible because using NSURLConnection instead of NSURLSession)
My app uses Alamofire 3.42 to make our API calls along with a host of other frameworks. All the frameworks and our server are IPv6 compatible and yet our app fails for the Apple Testing team when tested in an IPv6 only environment.
We have tested our app in a NAT64 as prescribed by Apple with successful outcome. Our packet trace too shows IPv6 addresses being called successfully and yet our app update keeps getting rejected again and again.
When we submitted the app the first time, it did get rejected once for the IPv6 issue but got accepted the next time we submitted. Although, now we are trying to submit an update which keeps getting rejected with only this issue being quoted.
This has taken a lot of our time and would really appreciate some help with this. TIA!
I currently have a production phonegap app (3.3.0) installed on an iPad. It's sends an ajax request to sync data to a server. No updates have been made to the app or server but for some reason it's stopped connecting to the server. The iPad can connect through safari with no issues.
I've read information regarding a whitelist on the app though I never had this in place and we never had an issue. Other iPads with the same version of the application are connecting with no issues.
My initial thoughts were a update was made to the iPad which blocked access, though there are no restrictions in place. Anyone seen this type of issue or any thoughts on what the issue could be?
There is data with the local DB we need to retrieve so I don't want to re-install the app as I'll lose the data.
Any help would be appreciated.
Thanks,
I am new to phonegap and coding so I am unaware as to how to use PhoneGap. First of all what I did was connect my PhoneGap (desktop) app thing to my iPhone PhoneGap developers app. On my iPhone it just says downloading... there is nothing else happening. I then tried using an Android phone to see if it works but it just says
unable to download archive from the server.
unable to properly connect to the server.
I dont know what to do so any help will be appreciated.
This can be caused by many things.
I assume you followed the steps from http://app.phonegap.com/ site:
you have created a phonegap app (at least a sample one using 'phonegap create')
you have a server running (using phonegap desktop or 'phonegap serve' from command line)
There are some things you have to check in order to know what is wrong:
Both the devices must be in the same network to 'see' each other.
The firewall is turned off or allows communication on the port the server is running on (default is port 3000)
Check if your antivirus isn't blocking the same port.
If you still have no connection here is the survey/checklist you should go through. It helps you get closer to the center of the problem you have (points: 7-11).
If that does not help you can always fill an issue (and attach above-mentioned survey) but I strongly recommend reading documentation first