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)]], const device
Search results for
Visual Studio Maui IOS
105,638 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
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'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,
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 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.
The main cause for this terrible battery drain is a background app refresh - even if you turned it off it does operate (also you can see it in the Battery statistics)Just try to turn it on and off and check a result.---and now I'm restoring to ios 8.4
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I had this same problem on iOS 8.3 and iOS 9 to fix it you must un-pair your Apple Watch and then re-pair it you can restore from a backup it won't affect it. This fixed it both times for me. Best of luck!
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I talked about Linux and Visual Studio / Windows. How did you get the idea I was saying LLVM was much further along with BSD which I did not mention. LLVM is coming to windows by Google and now Microsoft - but Linux is much further along than .... Windows
Topic:
Programming Languages
SubTopic:
Swift
Tags:
Check the Target Platform of your framework and watchkit extensiosn in their Build Settings.It seems currently Xcode 7 only lets you choose either iOS or watchOS, but since your framework is shared between platforms you need to manually put all 4 of: watchsimulator, watchos, iphonesimulator, iphoneosIn my case, after fixing the above, I also needed to add armv7k and i386 to Valid Architectures.Then I finally got to see all the new WatchKit compile errors 🙂
Topic:
App & System Services
SubTopic:
Core OS
Tags:
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
Ok so here is the fix for my problem. After installing beta IOS 9 to the phone set it up as a new phone. Sign in to your icloud account and individully download apps and music you want tested on the phone and the carrier will stay. If restored from a back up the carrier will drop everytime. I hope this helps others with similiar issues.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Ok so here is the fix for my problem, it may work on yours. After installing beta IOS 9 to the phone set it up as a new phone. Sign in to your icloud account and individully download apps and music you want tested on the phone and the carrier will stay. If restored from a back up the carrier will drop everytime.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
When you close all the app in the multitasking window you really thought that it closes all of the apps but it didn't when you open Settings for example and swipe your four fingers to the left/right of the screen you will go back to your recent app that you surely closed earlier, And when you open the multitasking window the recent app you closed is back.
This sounds like a Radar to me. I am having the same issue. I had compiled this for the WatchKit Extension under iOS 8 + WK. I'm guessing there is a bit of unimplemented foo between the seed 1 release and the conference demo seed (Usually a few builds later)Work around seems to be temporarily to move that functionality over to the iOS app and WatchComm it across.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
When you go to Settings > Battery TIME SINCE LAST FULL CHARGE it doesn't show anything although how many full charge your iPad or device will be.