Please dupe my radar!

This bug has been closed as Duplicate. We are aware of this issue and are tracking it under the Bug ID listed below in the Related Problem section of your bug report. To check the status of the original bug report, please visit the Related Problem section of the Problem Detail view of your closed duplicate bug.

DUPLICATE OF 10469407

Please verify this issue with the macOS Mojave 10.14 beta 6 and update your bug report at https://bugreport.apple.com/ with your results. macOS 10.14 beta 6 (18A353d) https://developer.apple.com/download/ Posted Date: August 6th, 2018 If the issue persists, please attach a new sysdiagnose captured in the latest build and attach it to the bug report. Thank you. macOS sysdiagnose Instructions: https://developer.apple.com/services-account/download?path=/OS_X/OS_X_Logs/sysdiagnose_Logging_Instructions.pdf For a complete list of logging instructions visit: https://developer.apple.com/bug-reporting/profiles-and-logs/

Apple Developer Relations August 29 2018, 1:56 AM No response received. Now closing this bug.

Confirmed fixed in iOS 12.0.1 (16A405)

The original report on your issue has been closed recently. Please note that you will not be able to directly view the original report in order to keep its information confidential.

Confirmed fixed in iTunes 12.9.0.164 on macOS 10.14 (18A391).

I have been experiencing this issue as well, but have not seen any reports of it from users running iOS 12. Perhaps it's been resolved? I'd love to hear if anyone else has seen this from an iOS 12 user.

From Apple:

Engineering has determined that your bug report (45048050) is a duplicate of 42858960 and will be closed.

102 Issue has reappeared in 2018 on latest version of iOS for 4S.

Engineering has provided the following information regarding this issue:

"spm" was indeed considered but ultimately rejected. The discussion can be found in the alternatives considered of this proposal: https://github.com/apple/swift-evolution/blob/master/proposals/0085-package-manager-command-name.md#alternatives-considered

Creating Sandbox Test account now working as expected. Able to create new accounts and newly created account displays on the list.

There's still a bug, but I've found a work around. Have ticked "Base" for the intent definition file, therefore moving the .intentdefinition file to the Base.lproj directory instead of en.lproj. Everything now seems to work correctly for languages we support, and those that we don't.

Console:

`2018-10-12 13:54:41.313421+0800 Intents Extension[1061:22075] [Intents] INSchemaWithTypeName Did not find schema inside of bundle URL: "file:///private/var/containers/Bundle/Application/3995A903-CCCC-400D-A123-70AAAA387C97/MyApp.app/PlugIns/Intents%20Extension.appex/" 2018-10-12 13:54:41.314191+0800 Intents Extension[1061:22075] *** Terminating app due to uncaught exception 'NSUnknownKeyException', reason: '[<DailyBriefingIntentResponse 0x1460568f0> setValue:forUndefinedKey:]: this class is not key value coding-compliant for the key briefingDescription.' *** First throw call stack: (0x21d409ed0 0x21c5d9a40 0x21d3239ac 0x2287072d4 0x228707404 0x2286caad4 0x1028d573c 0x102870f28 0x2285eeb48 0x2285f03f0 0x21ce436c8 0x21ce44484 0x21ce1efb0 0x21ce1faf4 0x21ce27f14 0x21d0260dc 0x21d028cec) libc++abi.dylib: terminating with uncaught exception of type NSException `

This issue was fixed in Xcdoe 10.1-beta 2, check the release log: https://developer.apple.com/documentation/xcode_release_notes/xcode_10_1_beta_2_release_notes#3038341

I am experiencing something similar on iOS12+ Universal links always failed for me within 5 minutes after rebooting the phone. I put descriptions in http://www.openradar.me/45201697

+1

This is affecting us, as well.

This bug is still occurring in iOS 11 and even iOS 12

Attached project: https://github.com/strongapp/Radars/tree/master/45120729

Apple Developer Relations August 30 2018, 12:47 PM This appears to be happening because the Pulley framework your test bundle depends on requires a different set of Swift libraries than the test bundle itself does, and the project is configured to only look at the test bundle and its embedded contents when determining which Swift libraries to make available. You could potentially fix this by having the Swift libraries also be embedded in the dependent framework (via the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES build setting), or by embedding Pulley.framework into your test bundle via a Copy Files run phase.

Tracy Keeling August 31 2018, 9:27 AM I tried adding a dependency on on the Pulley framework, but the error still occurs. I also tried linking TestAppTests with Pulley directly, but that didn't seem to help either. Setting ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES in the Pulley framework to YES does seem to work. This is not ideal, though, for an app that has a lot of frameworks (embedding swift libs into each framework adds significant size to the app).

Apple Developer Relations September 3 2018, 5:53 PM Engineering has the following feedback for you: A build-time dependency on Pulley.framework is not sufficient. You will need to embed Pulley.framework into TestAppTests (e.g. with a Copy Files build phase) for its Swift stdlib dependencies to be picked up.

Tracy Keeling September 4 2018, 8:28 AM Sorry, I did embed it. The only way I could get it to work was if I both embedded the Pulley framework AND set "ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES" on Pulley to YES.

Apple Developer Relations September 5 2018, 1:50 PM You’ll either need to match up the SWIFT_VERSION across your project or use ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES as mentioned. We changed the Pulley framework to use SWIFT_VERSION=4.2, upgraded the project, built, and tested your app successfully. This isn’t the best behavior, but mismatching Swift versions can be a bit finicky.

Tracy Keeling September 7 2018, 8:01 AM Pulley doesn't build with Swift 4.2 out of the box. If I update all of the targets to be version "Swift 4" I still get the same error.

Apple Developer Relations September 10 2018, 3:50 PM If you can’t update Pulley to Swift 4.2, then you need use the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES to override the behavior of Xcode and copy the libraries in.

Tracy Keeling September 10 2018, 4:12 PM I figured out a way to do that only in Debug mode so as not to bloat our app when compiled in Release mode. However, I still feel like this is a valid bug in Xcode 10.

https://bugs.swift.org/browse/SR-8962