After I update XCode to get iOS 6 SDK, I see that iAd is not loaded anymore on simulator. I can't try on real device for the moment as I've not updated my iPhone yet.
I didn't find anything about it on the release notes.
Anyone encountring the same issue and resolved it ?
This is a post from a moderator of developer apple forum :
Initial fill rates will reflect the recent launch of iOS 6. Thank you for your patience as we continue to ramp up ad serving.
It seem that ads will appears soon.
I got the same problem with the ads that I have on apps in the app store and newly created apps. After going through the iOS dev forums, and like a few have stated on here, basically its a server issue with apple. There is nothing we can do but wait it out. This is even causing errors in newly created projects as well.
The problem I see is the error is always returned with iOS 6. Both in simulator and on device. When using the iOS simulator with iOS 5.0 a test ad appears as expected. I no longer have an iOS 5.0 device to verify that the behavior is the same with it.
Related
but I have an iPhone 13 plugged into my MacBook Pro. I know this might seem like a strange question, but when I try to build & run my app the following messages notify me
This iPhone 4 is running iOS 15.6.1 (19G82), which may
not be supported by this version of Xcode. An updated
version of Xcode may be found on the App Store or at
developer.apple.com.
I cannot remember when the following notification came to my attention, but it basically displays the same message and I took a screenshot of it when it occurred
I have contacted Apple, but I am on my second tech, who is asking me about my browser version, etc... which tells me that they are stalling - no browser, an app build & run in Xcode. An app literally targeting iOS 11.0 and above
I am trying to write the XCUITest test case for Microsoft SSO login but my Xcode getting crashed every time if navigating on the SSO webpage or any other safari page from the application.
Some developers already reported this bug on the Apple forum for Xcode 9.3.
As per the Apple Xcode 10 release note, they have resolved this bug in Xcode 10.
https://developer.apple.com/documentation/xcode_release_notes/xcode_10_release_notes
I have tried with both Xcode 10.3 and Xcode 11.1 and getting the same issue every time.
I am able to record the SSO login automation element somehow using below trick-
I have recorded the element using the iPad instead of the iPhone and it's working fine for me. I know this is a weird solution but working for me.
When I run WatchKit App, Apple Watch simulator stuck loading. Like this,
But, I can run that for the first time, that is, it is the first time after restarting iOS simulator.
If you quit iOS simulator and then restart that, you can run Apple Watch simulator only once.
Now I need to restart simulator every time. That's really annoying.
Is there any good method for this situation?
Version 8.4 (SimulatorApp-565.9 CoreSimulator-117.15)
When this happens to me, I am usually successful after the second or third launch of the app (without quitting Xcode or the simulator). This has been the case with both Xcode 6 and Xcode 7.
If you provide more details, I can probably refine this answer better. Here are some things that may work for you, depending upon whether you're running Xcode 7 or 6:
Try deleting and re-creating the target scheme: SO: Apple Watch Simulator Issue
A variant of the above: Tutorial on Apple Watch from Natasha the Robot
Some suggestions that have worked for some people on Xcode 6.x: SO: watchkit simulator won't load app
Regardless of the work-around, if this isn't due to user error, perhaps the best thing to do is to submit a bug report to Apple.
Here are some suggested files to include when submitting a Radar Bug Report to Apple (See this developer form thread):
~/Library/Logs/CoreSimulator/[UDID of Watch]/system.log
~/Library/Logs/CoreSimulator/[UDID of Phone]/system.log
~/Library/Logs/CoreSimulator/*.log
A sysdiagnose taken just after reproducing this issue.
Does anyone know of a definitive way of restoring a device back to iOS 6 from iOS7?
I've already got the correct ipsw file for the device, for iOS 6.1.4 (the latest pre-iOS 7 version of iOS 6). When I try and restore through Xcode's Organiser window, I get the following error after selecting the 6.1.4 ipsw for restoration:
iOS: Restore error 3194 or 'This device isn't eligible for the requested build'
I've been to the following article (http://support.apple.com/kb/TS4451), but it doesn't really shed any light on the matter.
I know standard users are struggling to go backwards, but surely there's a way for developers to get back to iOS 6?! Without just avoiding doing any updating?! Surely?!
Am I just being naive or a bit thick here?
It is not possible to downgrade from a newer version of iOS. Initially, there is a grace period where Apple signs the installation of an older iOS version, however for the iOS6->iOS7 transition, this grace period has expired.
For the future reference, always make sure to keep at least one development device unupgraded, so you can continue testing.
My game is crashing at launch on iPads for some users with some mystical reason.
But it works fine on iPhone (iPad and iPhone versions are different apps, but technically is the same builds, just different targets)
It happens after updating the app to version 1.1.1
The game had previous updates which works correctly. (updating few months ago 1.0 -> 1.1 was perfect)
Version 1.1.1 was created for iOS 6 compatibility- Landscape GameCenter bug + added few SDKs (Urban Airship, Flurry, TapJoy etc) + app name was changed
As far I know - crash happens for users who updated their iPads to iOS 6.0 and updated the game after that.
App update process working fine for me and few other test devices, but a lot of users experienced the crash and wrote 1* comments in App Store.
Bug was unable to reproduce.
One more weird thing:
Only thing I have is single crash report.
Please help me to read it, I will be really appreciated!
Download crash report here
I've had similar problems with flurry and only figured it out after adding a crash reporting SDK to my app. I've tried a few. Here's a decent free one:
www.crittercism.com