I'm trying to add a device (iPhone 5) by the UUID, but the the loader never stop loading. I am not doing anything different then I normally do, but I feel like the loader will never stop since I have been waiting for a long while now.
Is there something wrong with my account or whatever or...
Thanks in advance
Use safari and not chrome, at least that seemed to be my issue.
Somehow the Apple developers site is having some issues with Chrome.
If you want to cut out the browser from this task completely you can have a look at Cupertino, part of the Nomad-cli toolset. Amazing work from #mattt
https://github.com/nomad/cupertino
Related
I'm not sure this question can be asked here, but I dont really know where I can get information. I've been doing some research and nothing obvious came out.
So here is the thing, I've developed a functionnality.
It works fine on computer.
It works fine on the Android Api.
But there is some bugs on the Iphone Api.
The thing is: I don't have any Iphone, so I can't see what's happening. Jus know what people said to my boss.
So, I'm looking for a piece of software to be able to test the API like if I was using an Iphone. I'm not just looking for something that will simulate sizes like the view from navigator development functionnality.
Do you know something like that ? It will be really helpfull thank you.
You need an apple computer.
Open up the project in Xcode which has an emulator.
Otherwise:
If your windows, you could try an app like Smartface: https://www.smartface.io/ios-and-android-emulator-on-windows/
Google iOS Emulators for Windows for Development and you should have lots of options to review for yourself.
The iPhone simulator in xcode should be exactly what you need.
This should get you started:
https://developer.apple.com/library/content/documentation/IDEs/Conceptual/iOS_Simulator_Guide/Introduction/Introduction.html
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 apologize for this not being exactly a programming question
I have a few apps that I'm deploying internally in our org using ad-hoc distribution with Enterprise account. What worked in iOS6 now creates two icons: one a normal app icon and another one is a weird default icon that has the same name as the main app. Clicking on this icon does not do anything. See attached screenshot (it only has the gray icons). I can remove the app through conventional means (long press and then the "X" icon), but I can not remove the gray icons.
Does anybody know what are those, and how do I get rid of them?
I had the same problem. The fastest way to get rid of these ghost or dead icons is to make a backup of your iDevice and then restore it.
I tried every hint i found with google and nothing helped but the restore. So my advice: Don't google anymore, just backup & restore ;-)
yes, we see that too. often but not always. it definitely looks like a bug
as for getting rid: no really good way...
restart the device, rearrange, delete a few times and wait a few days. a combination of that did the trick for a few phones here
no real solution except for apple to fix it :D
I found a reproducible way of causing this problem.
For me, it appears to be linked to the plist used for over the air distribution.
If you generate it through XCode/Archive/Enterprise Distribution, it works normally.
If you subsequently update the ipa, but keep the old plist, you will get this issue if you did one or more of the following:
1) change bundle identifier
2) changed the mobileprovision used to compile
3) changed the app version
Can anyone confirm? Or is this only happening to me?
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.
This guy seems to have a similar problem, except mine doesn't work at all, not just on the first try. Today I installed xcode 4.2/ios simulator 5.0 hoping that would fix the problem, but it hasn't helped. The app has consistently run on actual devices, but all the developers who own Iphones are out of the office today and the company ipod is in use elsewhere.
I've tried closing both xcode and the ios simulator, changing between 5.0 and 4.3, changing between regular iphone and iphone retina, trying with simulator running first and trying with simulator closed first. It just sits there on the loading screen. As far as I know the simulator has never worked, I'm not the one who setup xcode or any of the devices (he doesnt work on Mondays and didn't know how to fix it on Friday anyway). Any help would be appreciated.
Turns out adding "localHosts" to ExternalHosts fixed the Simulator, but the simulator doesn't like the ajax call to our services site, so it still isn't working, but now at least we have an acceptable reason for it. (Devices work correctly, so it isn't that big of a deal) Hope this helps someone.
If anyone can think of a way for the simulator to work with the reference to external calls I'll transfer the answer to their answer :P.
Like Luke said in a comment to you: just use JSONP.
It's not the simulator's fault, that's just how browsers work. They don't allow cross-domain ajax requests. That's why there is a solution to this problem, namely JSONP. In essence, the response must be a regular JSON object that is enclosed in a function call, something like callback_function({json: 'object'}).