Seems to also crash on images :(

Duplicate of rdar://49604334

This would be a great feature to have. Setting up Apple TV's 100% touch-free would be very nice. In a large school district with 500 new Apple TV's coming in this year alone would be a life saver for our techs to have.

"We’ll keep this bug to consider your feedback about how this API works, but the caller is expected to delete the directory created with .itemReplacementDirectory when you’re done using it."

A solution is under investigation. We will follow up with you again when it is available.

Thank you for filing this report. Much has changed since the report was filed, and we are closing it. If this is still an issue for you on current releases, please file a new bug report. If you have questions regarding the resolution of this issue, please comment in this bug report. Thank you for taking the time to submit bug reports. We appreciate your input.

YES! we need this!

Any update on this? or any workaround?

I added mediaPlaybackRequiresUserAction and with iOs 12.2 the video not being played :(

Thanks!

I received communication from Apple around this issue and have verified it has now been fixed.

This is how you should initialize AVAudioRecorder if you want to set the bitrate

let recordSettings = [AVEncoderBitRateKey: 32000, AVFormatIDKey: kAudioFormatOpus, AVSampleRateKey: 16000.0] as [String: Any] let recorder = try AVAudioRecorder(url: url, settings: recordSettings)

Also, if you want to set the bitrate to be constant, add AVEncoderBitRateStrategyKey: AVAudioBitRateStrategy_Constant to the recordSettings dictionary.

Also take a look at http://openradar.appspot.com/50553219 which demonstrates a limit to the number of temp directories which can be created with this API.

You can get the test files here: https://github.com/aonez/Keka/issues/403#issuecomment-489988988

Any updates on this?

Happening for me as well, lot of things getting impacted, and yeah only happens on XS, XS Max, and XR

Response:

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

The open or closed status of the original report your bug was duplicated to appears in a text box within the bug detail section of the bug reporter user interface. For security and privacy reasons, we don't provide access to the original bug yours was duped to.

If you have any questions or concerns, please update your report directly at this link: https://bugreport.apple.com/.

This was marked as a duplicate but I can't find the duplicate. This issue still exists as far as I can tell. Is anyone at Apple looking at it?

This happens very reliably on Version 10.2.1 (10E1001), and I’m including rdar://50407410 on every crash now.

Hi Yurii,

This is a follow-up to Bug ID# 49603345 - English and Japanese(English) keyboard have different character set input. FIRST-16601

Engineering has determined that this issue behaves as intended based on the following information:

We took a look at the attached video. The keyboard is behaving correctly. We would suggest that you read the article here: https://en.wikipedia.org/wiki/Halfwidth_and_fullwidth_forms

We consider this issue closed. If you have any questions or concern regarding this issue, please update your report directly (https://bugreport.apple.com).

Thank you for taking the time to notify us of this issue.

Best Regards,

Developer Bug Reporting Team Apple Worldwide Developer Relations

Xcode 10.2.1 still have the issue

• This dylib is not new, it has been in the toolchain since Xcode 9.

• The header is not bundled with Xcode because it is not considered a supported stable API. With ‘not supported’ I mean that, unless stated otherwise, frameworks and dylibs contained inside the Xcode.app bundle are considered internal implementation details and we reserve the right to completely change them between Xcode versions (the ABI may change or the framework/dylib eliminated entirely, etc.).