Recent Comments

Open Radar 40881008: keep Library window open if I press option after starting drag

Implemented in Xcode 10 beta 4: pressing option during the drag brings the library window back.

Open Radar 40880961: pin the library floating window open

Implemented in Xcode 10 beta 4: hold option while opening the library, or hold option while dragging and it'll stay open after.

Open Radar 35038472: UICollectionView with self-sizing cells resizes cells during insert/remove animation or performBatchUpdates

I'm experiencing the same, though only on physical devices. Oddly, inserting self-sizing cells on the simulator works perfectly.

By Tooley7 at July 17, 2018, 2:16 p.m.

Open Radar 41794584: Opening Maps.app for directions fails when Maps.app not launched

Apple

Engineering has determined that your bug report is a duplicate of another issue and will be closed.

By futuretap at July 17, 2018, 8:41 a.m.

Open Radar 41794584: Opening Maps.app for directions fails when Maps.app not launched

My response

While I don't have the time to create, sync and upload a sysdiagnose, you can easily reproduce this using our Where To? app. For your convenience, I'm attaching a promo code for a free download from the App Store:

[redacted]

Install the app, select any place, tap the directions button and select the Maps app for directions. This will be much more convenient since you can then debug the issue right away.

By futuretap at July 17, 2018, 8:40 a.m.

Open Radar 41794584: Opening Maps.app for directions fails when Maps.app not launched

Apple

Please reproduce the issue, trigger a sysdiagnose and attach the log file to your bug report. Also, if the bug can be seen visually, please include a screenshot and or a video of the issue.

(…)

By futuretap at July 17, 2018, 8:40 a.m.

Open Radar 42087654: Jump to definition with pre-compiled Swift modules results in SourceKit error

I was just experiencing https://openradar.appspot.com/42088037

By keithbsmiley at July 14, 2018, 8:53 p.m.

Open Radar 37534672: SKReceiptRefreshRequest may damage a mac app

Developer Relations

We believe this issue has been resolved in the latest macOS 10.14 beta.

Please test with the latest beta. If you still have issues, please update your bug report with any relevant logs or information that could help us investigate.

macOS beta https://developer.apple.com/download/

By hannes.oud.dev at July 11, 2018, 5:05 p.m.

Open Radar 35826524: restoreCompletedTransactions() does not refresh receipt if no IAP were made

Apple Developer Relations

restoreCompletedTransactions is not meant to refresh the receipt. It is meant to replay transactions that have already gone through. If there are no transactions to replay, there will not be a receipt in the server response. If the receipt must be refreshed use SKReceiptRefreshRequest. This bug was used to fix the issue mentioned above where restoreCompletedTransactions would always fail if no account was signed in.

By hannes.oud.dev at July 11, 2018, 5:03 p.m.

Open Radar 32830264: Enable eGPU Device Support in Boot Camp

This is quickly becoming an imparitave feature. There has been o much push by Apple for eGPU in macOS, they need to support all aspects of their hardware. Including windows support in boot camp. For sales and functionality this is a must at this point!

By dogbots159 at July 9, 2018, 4:06 p.m.

Open Radar 41019421: Creating asset from file URL creates weird filenames (not IMG_xxxx.yyy)

I replied:

Thanks for the reply. Yes, this is still an issue for us.

That said, if the original filename is not DCF compliant, it will get a DCF compliant name when transferred using Image Capture.

We are aware of this. Our issue is that the DCF-compliant file name that's being generated appears to be a "random" combination of letters and numbers, such as "HMTZ3319.JPG" or "LQTI4681.JPG". These filenames have no order and no apparent relation to the "usual" naming scheme "IMG_xxxx.JPG".

We'd like the file names in Image Capture to always follow the consistent scheme of "IMG_xxxx.JPG", regardless of which API is used for creating the asset. Many of our customers transfer photos using Image Capture and prefer a consistent file naming scheme.

Thanks for looking into this.

PS: In thinking about your reply, it occurred to me that I don't even know if the file name that appears in Image Capture is set by Photos.framework when the asset is created or if some other iOS component generates these file names "on the fly" when Image Capture or a similar app connects to the device. I can only report the behavior we're seeing when using the Photos APIs to save assets.

By ole.begemann at July 9, 2018, 3:52 p.m.

Open Radar 41019421: Creating asset from file URL creates weird filenames (not IMG_xxxx.yyy)

Apple replied with this message:

This issue behaves as intended based on the following:

File names shown by Image Capture are limited by the PTP protocol. The file names must conform to the DCF (Design rule for Camera File system) protocol: https://en.wikipedia.org/wiki/Design_rule_for_Camera_File_system

Also, you should be setting the original file name. We do try and use that when exporting assets out of Photos. That said, if the original filename is not DCF compliant, it will get a DCF compliant name when transferred using Image Capture. Note that using addResource(with:fileURL:options:) will set the original file name from the URL, if not provided.

Please update your bug report to let us know if this is still an issue for you.

By ole.begemann at July 9, 2018, 3:51 p.m.

Open Radar 41651051: Xcode should offer a fixit when you attempt to use a Swift-only member from Objective-C

My response to them

That's fine, but if there is no legal Objective-C selector, and you attempt to use a Swift selector, Xcode could at least emit a warning about it.

By heath.borders at July 9, 2018, 2:46 p.m.

Open Radar 41651051: Xcode should offer a fixit when you attempt to use a Swift-only member from Objective-C

Apple responded

Engineering has provided the following information regarding this issue:

This is deliberately not implemented. Since Objective-C methods are identified by class and selector, noting that a particular selector comes from Swift could interfere with an Objective-C category elsewhere in the project that tried to provide that selector. It is unusual but permitted for Swift and Objective-C to define methods that would have the same selector, but to then not expose the Swift method to the Objective-C runtime.

By heath.borders at July 9, 2018, 2:45 p.m.

Open Radar 23412056: UI Tests fail to run when project is first created with a Framework, and application target comes later

To fix this I had to create a new Copy Files build phase in the UI tests App target (not the UI tests target). That build phase copied the framework to the Frameworks destination.

By maarten at July 9, 2018, 11:35 a.m.

Open Radar 32830264: Enable eGPU Device Support in Boot Camp

Enable eGPU Device Support in Boot Camp

This is something we Macbook owners need. I have been a Macbook user for over 10 years, but the throttling of the eGPU capabilities in bootcamp will make me thing twice before buying another Apple product.

By caineknight at July 7, 2018, 8:03 p.m.

Open Radar 41032092: XCTest Randomized Execution Order: Rerun with same order

Duplicated: 41928381

https://openradar.appspot.com/radar?id=4940420333174784

Open Radar 34994712: CLLocationManager.deferredLocationUpdatesAvailable() Always Returns False

Update from Apple Developer Relations: Engineering has provided the following feedback regarding this issue: This feature was removed in iOS 10.