İOS 26 beta battery %1

On iOS 8, this code (Swift) worked:let shaderString = void main() + { + gl_FragColor = SKDefaultShading().bgra; + } let shader = SKShader(source: shaderString)Now on iOS 9, with Metal under the covers, I get this error message:2015-06-09 18:36:39.497 TestVideoCam[550:63920] Jet: Error Domain=MTLLibraryErrorDomain Code=3 Compilation failed: program_source:6:321: error: use of undeclared identifier 'SKDefaultShading' fragment float4 SKShader_FragFunc( texture2d<float> u_texture [[texture(0)]], const device float *u_time [[buffer(0)]], const device float2 *u_sprite_size [[buffer(1)]], const device float *u_path_length [[buffer(2)]], SKShader_VertexOut interpolated [[stage_in]]){return SKDefaultShading().bgra;} ^ UserInfo=0x156e50c10 {NSLocalizedDescription=Compilation failed: program_source:6:321: error: use of undeclared identifier 'SKDefaultShading' fragment float4 SKShader_FragFunc( texture2d<float> u_texture [[texture(0)]], const device float *u_time [[buffer(0)]], con

So, I followed the install ios beta software and watchOS beta software LINE for LINE.I did add UDID for both to Certificates, Identifiers & Profiles. I even have a screenshot to prove it, if I need to.I tried hard booting ( hodling the crown and side button for 10 seconds until the apple symbol comes up ) several times.So, am I screwed? Is there a way to get off the REPOD?

I didn't see anything obious so far except for possibly multitasking, which I am going to ask if it is/has usable background modes, is there any new background modes in iOS9, you know the kind, the kind that our users are begging us for? it always amazes me the answer to someone here asking if they can do something in the background,and the answer is that this does not fit into Apple's plan for the battery. yet the task asked about, would take far less battery than the current background modes, or even the task itself by having to do it in the foreground using the display. for instance doing a specific task that lasts less than 10 seconds at a specific date and time in the future, which uses about 1/1000th the battery of even major change to location in the background ...right now I have to ask the user to spend 10's of times the amount of battery than they have to, to execute tasks, because I am forced to have the user use the display to do it, rather than to do a

I'm playing with the new Split Screen feature of iOS 9 for the iPad Air 2. While my Apps works fine in general in all supported sizes, I do see a weird behaviour of UIPopoverControllers. If my App only gets half of the screen, all Popovers are opened no longer as a popover window, but instead are opened like they would be presented modally. Which means they take over the whole screen area which is reserved for the App. This is a problem because a popover does not have a close or done button (you close it by tapping outside of the popover), but a modally presented controller can not be closed without a done or close button. So while my App is in half-screen mode, I can no longer close the popover controllers. Can I force the iOS to present the popovers as popovers in this case? The half screen has a width of 507 pt, the popovers usually have a width of only 320 pt, so it is plenty of room to still present these as popovers. And if I can not force the iOS to present these as popovers,

The one item I was looking for with 10.11 was the ability to turn off Inline attachments in Apple Mail for OSX. Maybe I am in the miniorty, however all I would like to see is the ability to send attachments other than INLINE in the email body. Even a simple switch in preferences would be great, but after years of mail imporvments this has never been added. Apple can this be added as a future item, like 10.11.1 or something?Thank you! 🙂

Updated an app to iOS 9 / Swift 2 / watchOS 2 and since then, Xcode claims it can't find my embedded framework when building the watchOS extension. It has no issues finding it for my iOS app and the build settings look ok - the framework is showing as a dependency... but yeah, no dice. Tried cleaning and nuking Derived Data.Any ideas?

I've had an Apple ID for yeas, and the credit card, email, etc I used for creating it is not the same I want to use to enroll in the Developer Program.Also, does information like the home adress in the billing need to be exactly precise? or it doesn't matter that much?Thanks.

Hi, all, I see I'm not the only one with serious issues with the new watchOS (should have called it an alpha release IMHO). In addition to no notifications and no messages, my contacts never imported. Does anyone know how to force the watch to do something like import contacts? The general voodoo aspect of doing any activity on the watch (as a user here, not a developer) is extremely frustrating. There is simply no indication of what is going on, what might be wrong, or how to fix anything. With luck someone will know a solution to this. With more luck, we'll have a beta 2 of this software out SOON.

I what to learn programming for OS X, iOS, watch os. I have no programming experiance. What is the best place to start? Best courses, etc.

Network securityHTTPS, TLSIn 2015, TLS is a minimum baselineMany servers default to TLSv1.0, from 1999Newest version is TLSv1.2TLSv1.2 is not enough. Compromise of a server key lets you decrypt all TLS traffic that was encrypted in the past.With forward secrecy, a server key compromise will only let you read future traffic. Past traffic will not be able to be decrypted.By default, apps linked against iOS 9 and OS X 10.11 cannot make unprotected HTTP connections.TLS connections will need to comply with best practices- Exceptions can be declared on a case-by-case basis in your app's Info.plist file.System Integrity ProtectionDefense in DepthSecurity is about layersOne layer failing shouldn't defeat all securityRely on multiple layers of protectionDelay the attackerReduce your attack surfaceSeque into talking about Vauban and star fortresses. History lesson FTW.OS X's star fortress security model:Outermost line - Developer ID and GatekeeperSecond layer - Sandbox - attacker only gets access to the data w