Hello, I'm encounter crashes when integrating a company internal package through SPM only when I compile my app with the release scheme. My solution so far was to directly integrate sources into my project to solve theses crashes. For the context, the library use Metal and AVPlayer to manipulate AVPlayerItem and render video. Crashes frequently happened on those following lines: self.playerItem = AVPlayerItem(asset: asset) self.videoOutput = AVPlayerItemVideoOutput(outputSettings: [ kCVPixelBufferPixelFormatTypeKey as String: NSNumber(value:kCVPixelFormatType_32BGRA), kCVPixelBufferMetalCompatibilityKey as String: NSNumber(value: true)]) self.playerItem?.add(self.videoOutput!) The videoOutput variable is becoming nil resulting a crash. I have tried to disable compilation optimization of Apple Clang and Swift Compiler in the app and in the package (I don't know if compilation parameters of a package have any influence at all). I tried this because theses compilation parameters are different in release
Search results for
file uri scheme
79,849 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Not all the Map app settings are surfaced in the URL scheme so please file a bug report asking for this feature. I know it's not what you're looking for but does dirflg=w give you an appoximation of what you want to see? -M
Topic:
App & System Services
SubTopic:
Maps & Location
Tags:
Geting Xcode to recognise your source editor extension can be tricky. There are two cases to consider: Debugging Production I recommend you start with the debugging case. When you create a new source editor extension target, Xcode create a scheme for it. That scheme isn’t very useful out of the box. Do this: Use your primary copy of Xcode for this work. Ideally it’d be the one in the Applications folder. Select the extension scheme in Product > Scheme. Choose Product > Scheme > Edit Scheme. In the Run action, switch to the Info tab. On the Executable popup, choose Other and select your primary copy of Xcode. Make sure Debug Executable is not checked. Close the sheet and then choose Product > Run. Xcode should launch a second copy of itself. In the Dock, you’ll see the icon with an orangey tint. Bring that to the front. In this copy, open a test project and navigate to a source file. Your extension should be visible at the bottom of the
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Bug 27180467 submitted:NOTE: that there is no attached file in this forum, but it was attached to the bug report.Summary:Both Xcode 7.3.1 and Xcode 8 beta 2 are installed. Running a project on the 9.3 simulator in Xcode 7.3.1 works. However, closing Xcode and the simulator, then opening a different project in Xcode 8 beta 2 results in a loss of scheme setting, as shown in the attached file NoScheme.png.Steps to Reproduce:1. Start with Xcode 7.3.1 installed2. Install Xcode 8 beta 2 a. download b. drag Xcode-beta from Downloads folder to Applications folder c. run Xcode-beta3. Create an iOS project in Xcode 8 beta 24. Close Xcode 8 beta 25. Open Xcode 7.3.16. Run an iOS project (a different project not related in any way to the one just created in Xcode 8 beta 2) on a simulator (for example the iPad 2 (9.3) simulator)7. Exit Xcode 7.3.18. Exit Simulator9. Run Xcode 8 beta 210. Load the project created in step 3Expected Results:The Xcode 8 beta 2 project's Scheme should still
This would appear to be a content authoring issue or .m3u8 playlist issue. For debugging purposes only, to determine if it is a content authoring issue we recommend you set your EXT-X-KEY tag KEYFORMAT attribute in the .m3u8 playlist to identity instead of com.apple.streamingkeydelivery, add the initialization vector (IV) of the key you are using to the IV attribute, and set the URI attribute to an http URL pointing to a (16-byte) resource containing only the raw, unencrypted AES key. For example, instead of something like this:#EXT-X-KEY:METHOD=SAMPLE-AES,URI=skd://key67,KEYFORMAT=com.apple.streamingkeydelivery,KEYFORMATVERSIONS=1do something like this:#EXT-X-KEY:METHOD=SAMPLE-AES,URI=http://mysite.com/my16ByteKey.bin,KEYFORMAT=identity,IV=0xA30FE123ECBF1BE323A775A119C553BCand make your 16-byte key available on your mysite.com web server.This allows the client to receive the same content, but instead of decrypting it with FairPlay Streaming it decrypts it with a clear text AES key
Topic:
Media Technologies
SubTopic:
Streaming
Tags:
Select the phone scheme first, then select the watch scheme.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Are you trying to submit the archive build using the Watch scheme or the iOS scheme?
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I have a ton of issues Importing and Exporting Localisation files, and have burnt too many evenings ! I usually resort to the XCode command line , that seems pretty reliable .... I do a clean build maybe -SkipMacroValidation helps I cant recall ! /usr/bin/xcodebuild -sdk iphoneos -skipMacroValidation -configuration Debug -workspace my.xcworkspace -scheme myScheme build CODE_SIGNING_ALLOWED=NO Then an Import or export /usr/bin/xcodebuild -sdk iphoneos -configuration Release -workspace my.xcworkspace -scheme myScheme -importLocalizations -localizationPath path-to/my.xcloc CODE_SIGNING_ALLOWED=NO
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Sad nobody responded.What I ended up doing was creating several Core Data configurations:* Cache* Cloud* LocalCloud of course has the syncing enabled on it. So in your scenario, users can start off on Local and have it sync against the Cloud configuration in the background. Are you actually storing the entire file contents within Core Data? If so, you might want to move to a model of storing just a URI to an iCloud document, after-which a user accessing it can trigger a separate iCloud sync.I'm also fairly sure I saw documentation that there is a hard restraint on cloudkit record sizes as well.
Topic:
App & System Services
SubTopic:
iCloud & Data
Tags:
I have a custom url scheme for my app, prior to building with Xcode 10 when a user taps on a URL with the custom scheme my app would launch and a delegate call would be made to:```func application(_ app: UIApplication, open url: URL, options: [UIApplication.OpenURLOptionsKey: Any] = [:]) -> Bool```However, now that I am building with Xcode 10 this functionality is broken. The app continues to launch when a user taps on the custom url, however the open url method in my app delegate does not get called.I've been trying everything I can think of here and can't seem to figure out why it is not getting called. If I create a sample app using the same URL scheme it works just fine and open url is called. Something has got to be going wrong inside my app, some other item in my info.plist or build settings that could be interfering maybe?Has anyone else seen this?
It sounds like you've performed the right steps: Create the .storekit file Add the product metadata to the file Select the .storekit configuration file in your scheme's run options Run the app If you're not seeing it at this point, would you be able to collect a sysdiagnose - https://download.developer.apple.com/OS_X/OS_X_Logs/sysdiagnose_Logging_Instructions.pdf and then submit feedback - https://feedbackassistant.apple.com with that sysdiagnose attached? If you reply with the feedback ID we can take a look at it.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
More bad news: It isn't just the one .h file. If I select any .h file and use Product>Perform Action>Compile File I get an error 'headerFileName.h' is not a member of any targets in the current scheme that build for running. So it appears that the target is broken and doesn't know it has any headers. If I delete the target and re-build the project will XCode create a new target? Maybe one that works?
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Hi,I'm using prefs:root=WIFI url scheme in my app with prefs entery in info.plist and it works great .Does some uses this api? I just want to make sure its not a private Api...Thanks,Marat
Thank you for explaining. We discussed your case here and we recommend doing an archive build and then copying the app out of the archive. We expect this will give you the best results using code paths that are currently supported. You can copy the app out of the .xarchive by changing the file name ending from .xarchive to .zip. Then you can open the .zip file and copy the app into the Applications folder. Note ~ Searching on the web I found some folks talking about duplicating the run Scheme and changing the Build Configuration to Release and using the result from that. That may work in some cases, but it may not produce correct results in others. This is not a supported code path. We do not recommend using this duplicate Scheme approach.
Topic:
Developer Tools & Services
SubTopic:
Xcode
I've use following source code for directly move to iCloud in setting,it is working fine but i want know it is valid? Please reply me as soon as possible.[[UIApplication sharedApplication] openURL:[NSURL URLWithString:@prefs:root=CASTLE]];