I'm a bit surpised that there hasn't been a new beta (watch or iOS) this week.
No New Beta This Week
Yes, it's been roughly every 2 weeks so far:
- 6 August -- iOS 9.0b5 and watchOS 2.0b5 released.
- 21 July -- iOS 9.0b4 and watchOS 2.0b4 released.
- 8 July -- iOS 9.0b3 and watchOS 2.0b3 released.
- 23 June -- iOS 9.0b2 and watchOS 2.0b2 released.
- 8 June -- Apple announces iOS 9, watchOS 2.0
At best, it won't be much less than three weeks this time...
They're kinda busy elsewhere, I think...
Hope it's soon as the latest is a battery killer.
In previous years, it's been 2 weeks with the occasional 3-week step
Today is 3 weeks exactly and no new beta. Wonder what's going on.
There in an interesting explaination as to why there is a regular beta drought at around this time of year offered here: Re: iOS 9 beta 6. The meat of which is:
"For June and July, Apple develops their next major release via two forks- the beta fork and the secret fork. The secret fork includes support for the unreleased hardware. The last few secrets have been Siri for iOS 5, 4" support for iOS 6, Touch ID support for iOS 7, and large screen support for iOS 8. Now come August, Apple must begin the work of integrating the secret fork into the beta fork to create one release build. From the start of the integration until the iPhone September event, Apple is unable to release betas without disclosing secrets. For that reason, there are never any betas during that time. This takes about a month- 34 days for iOS 5, 37 days for iOS 6, 26 days for iOS 7, and 36 days for iOS 8. Therefore, you will not see anymore betas until the September event.
Does this approach have a cost? Absolutely. By stopping all seeding for a month, Apple does not allow sufficient testing of the release and near-release builds. This is why there are pretty much always battery life, WiFi, and performance problems when iOS goes public in late September that eventually get fixed towards Christmas. However, secrecy is absolutely essential to Apple's marketing strategy and must be maintained, even if quality suffers."
Can confirm your issues.
Also WCSession fails very often, especially if requests are made in rapid succssion.
WCSession is also completely unusable in the glance (always unreachable).
WCSession failing when making requests in rapid succession is not expected behavior. Please make sure to file a bug with a sample project that reproduces the problem, and report back here with the radar number and I'll make sure it gets routed to the right engineers promptly!