I have this very frustrating issue with iOS dev center. Every time I want to add a new iOS-device by its UDID the site gets stuck in the loading screen. This same problem occurs when I want to change an existing distribution profile. The site just goes "Loading" forever.
Considering that this occurs on all my devices (computers, mobilephones etc.) I would be very grateful if someone had any idea how to deal with this problem..
Are you using Safari? For some reason the dev site doesn't always play nice with other browsers like Chrome and Firefox
I had the same issue for some time now. Actually even it is get stuck the device is added to my list. So just refresh the page after a while to see if it is added.
I did a bit of research into what the underlying issue was with this on Chrome. Seems there are multiple parts to this issue.
Firstly clearing cookies seem to help (partly) it got me past one hanging loading screen (first step of adding a new device), however I was still hanging on the next step.
Further investigation with Chrome developer tools indicated that Chrome was refusing to load some content due to XHR restrictions. Seems that Apple mixes https and http content. I was able to get past that by click on the shield icon on the right on the address bar and telling Chrome to allow the mixed content.
Finally there was also an issue with X-FRAME-OPTIONS headers that are being sent in the response which generate the following errors
Multiple 'X-Frame-Options' headers with conflicting values ('SAMEORIGIN, SAMEORIGIN, DENY') encountered when loading 'https://developer.apple.com/account/ios/device/deviceComplete.action?returnURL='. Falling back to 'DENY'.
Refused to display 'https://developer.apple.com/account/ios/device/deviceComplete.action?returnURL=' in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN, SAMEORIGIN, DENY'.
There are a couple of extensions available to remove X-FRAME-OPTION headers, but I wasn't able to get those working and wouldn't really recommend it.
My guess is that this works ok on Safari as it's not as strict on the XHR and X-FRAME-OPTION rules.
Anyway hope that helps someone. I'm going to raise a support request with Apple to see if they can get it sorted.
I have same issue with Chrome and Safari on OS X but it works fine with Chrome on Ubuntu.
Try deleting the cookies in chrome settings.This has always helped me.
Related
I stepped over a post, that describes, how to add a notification, when in a Blazor Wasm an update is available. I exactly followed the instruction but did not modify service-worker.js but service-worker.published.js because I wanted to test it in production. I also added the "periodically check for updates" mentioned at the bottom of the post.
Everything works fine in Chrome, Edge and Safari but not in Firefox. When I upload an update, after a while, the service worker checks for updates and all browsers show the notification button. Clicking the button in Chrome, Edge and Safari results in reloading the updated page. Firefox gets stuck at the loading screen and displays the following errors:
Someone reported this as a bug at aspnetcore and since they found out it must be a Firefox bug also at bugzilla. There it was discussed and finally got the status fixed. But I still get this error with the latest version of Firefox.
How can I fix this?
My use case I am trying to decipher an api call through charles proxy but on an IPhone. Now some of these IPhone's I am getting a wierd error message
IO:Push Back Buffer is full
It happens only on one of the Phones and rest of the phones work perfectly fine. And they are specific to only some of the API calls. I had the same issue on Android and I had to reset the Android to get it to work. Not sure if anyone had an issue like this with Charles.
Phone: Iphone 6S
OS: 10
Screenshot of the error
I posted the same in google SDK help forum, you guys can go through the response here
detailed answer here:
ok now looks like one of my colleague found a solution for this problem . So lot of us were effected with this issue every now and then and problem with come and go away on its own and more over this seemed to effect only the Ad related Api calls.
Solution: We just deleted the all the cache and data from the Play Store App in the Device Settings -- Applications Manager --> Delete all the cache data in the pay services.
This basically took care of the problem immediately although it did crash the App for 2-3 times but worked like a charm after that. So now this does point to a Bug in the Ad mobs SDK where it builds this cache overtime and starts complaining about it when it cannot handle it.
I've been developing JavaScript for many years with OSX and Mobile Safari, and I've noticed Remote Debugging has ALWAYS been extremely inconsistent.
Currently, I am running Safari 10.0 on El Capitan 10.11.6, and iOS 10.0.2 (the latest), and I'm not getting it to work AT ALL. I actually hadn't attempted to use this feature for several months before recently, so not sure if maybe the feature is just completely broken now.
In the past, if you quit Safari Mobile, and quit Safari (desktop) both, then started them back up, sometimes it would begin working, and then sometimes continue to not work (shows "No Inspectable Applications", or device doesn't show in menu). I am NOT changing any settings between these steps, and I know they are what they should be according to documentation, and tips I've read.
Develop menu is on. Web Inspector is enabled. Fraudulent Website Warnings is off (someone suggested this has something to do with it). iOS is open, and on a web page.
I know other people who've encountered this exact problem again and again. It seems that it is clearly a bug that Apple needs to resolve. I know how to use weinre, and this is a great workaround; however, it is highly irritating to waste my time trying to get this to work several (many) times, and then have to give up, and go set up weinre every time (it happens a lot).
So! I've read through several StackOverflow topics on this (can't find them ATM), but none of them that I've seen specifically address the spottiness of this issue, or how to solve it once and for all.
So I've built this web app game with HTML 5 and javascript (mainly jQuery). It's meant to be used on an iPad in a location where there's no wireless internet (a museum).
I am using a cache.manifest file to cache all the files needed for the game to work. And on my desktop using both Chrome and Safari this works great. I can see all the files listed in the application cache in the debugger and the app runs perfectly without internet connection.
Testing it on the iPad's browser also gave good results. It seems to take a bit longer for the iPad to cache all the files but if you give it enough time the app works in safari on iOS in airplane mode as well.
Now here's the problem. When I install the app to the home screen and launch it from there the app doesn't work. Only the first page will run and when I try to go to the next one it'll fail and tell me I need internet. (The second HTML page is loaded after the map appears and you've chosen hall 1)
I've read that it might need to cache all over again if launched from the home screen so I've tried waiting for it to cache and then going to the next page. I've waited for 2-3 minutes yet it still didn't work.
You can find the app here. It's in Dutch so it might be a little confusing.
The manifest file is here.
Any help would be greatly, greatly appreciated! Thanks.
So I figured it out myself.
Turns out it was a real rookie mistake. I had some bad references to the cache.manifest file in some of the pages of the app. And on an iOS device that seems to cause some problems.
Pretty confusing since it worked fine in a regular browser. But lesson learned: iOS is very picky when it comes to little details and you need to have a reference to the manifest-file on every page.
I am working on a web application that allows offline usage by caching everything in the manifest file. I am running into a few problems I hope you can help me with.
The problem is that the webapp is very buggy when I add it to homescreen. The problems are:
Sometimes it wont show anything and it tells me to turn on wifi (I test in airplane mode). This seems to be happening randomly. Usually it works if I close the app, connect to the internet, restart the app, and then go to airplane mode.
Sometimes not the entire code is loaded and its all messed up. Rebooting the app always works in this case.
Sometimes there is missing content. First I thought it was simply not done caching everything before I went to airplane mode. But I already experienced a situation where it worked at first, but closing and restarting the app would make the content unavailable.
Its a real pain to debug since it only occurs when adding the webapp to homescreen and you can't really debug in webapp mode (as far as I know, tips welcome!). I have tested offline mode in firefox, chrome and on safari mobile (without adding it to homescreen) and there are no problems there.
By the way, I am testing all this on an iPad 1 with iOS 5 and the webapp is using jquery mobile. iOS 4 has been tested aswell and gave me the same problems, tho it seems to be a little bit better on iOS 5. The webapp always works as it should when connected to the internet so the problem is with the caching.
Any ideas anyone? Or maybe tips on how to debug in webapp mode?
For debugging Web App try this one! iWebInspector You can load Web App into this debugger. And it's free.
Solved the problem. The cache file wasn't formatted properly. I don't know how I could have missed it. Everything is working perfectly now.