Post not yet marked as solved
I have this problem too. The timedMetadata comes in with iOS 16 beta simulator but on a device with IOS 16 beta it is empty. I added a bug report with id "FB10369973" for this with Feedback assistant.
I provided to Apple code with Objective-C using observeValueForKeyPath and also a complete project with Swift using AVPlayerItemMetadataOutputPushDelegate to demo the bug. Both versions have no metadata on devices but in simulators.
Post not yet marked as solved
I guess ATTrackingManagerAuthorizationStatusRestricted means the device is under MDM (mobile device management) and will thus not ask the user for consent (not show the ATT prompt) but will return what is configured for this device in the connected MDM if you call ATTrackingManager requestTrackingAuthorizationWithCompletionHandler.
Apple's source code in ATTrackingManager.h says:
/*!
* @property trackingAuthorizationStatus
*
* @abstract
* Returns information about your application’s tracking authorization status.
* Users are able to grant or deny developers tracking privileges on a per-app basis.
* Application developers must call `requestTrackingAuthorizationWithCompletionHandler:` for the ability to track users.
*
* @result
* The current authorization status. If the user has not yet been prompted to approve access, the return value will either be
* ATTrackingManagerAuthorizationStatusNotDetermined, or ATTrackingManagerAuthorizationStatusRestricted if this value is managed.
* Once the user has been prompted, the return value will be either ATTrackingManagerAuthorizationStatusDenied or ATTrackingManagerAuthorizationStatusAuthorized.
*/
@property (class, nonatomic, readonly, assign) ATTrackingManagerAuthorizationStatus trackingAuthorizationStatus;
I learned from code level support how to fix it:
… When tvOS 14 added Picture-in-Picture Support (PIP), we made the default value for this value is ‘true'. This has broken the existing behavior for audio.To get around your issue, you need to explicitly set the property ‘supportsPictureInPicturePlayback’ (linked below), to false, on your app’s TVApplicationControllerContext.<https://developer.apple.com/documentation/tvmlkit/tvapplicationcontrollercontext/3192087-supportspictureinpictureplayback>let appControllerContext = TVApplicationControllerContext()appControllerContext.supportsPictureInPicturePlayback = falseSetting this will make the Now Playing UI appear again. … It looks like tvOS 14.0.1+ changed the default value for supportsPictureInPicturePlayback from false to true. The docs say default is false until now https://developer.apple.com/documentation/tvmlkit/tvapplicationcontrollercontext/3192087-supportspictureinpictureplayback
Here's what i did for testing with Apple's demo project:
function playMedia(extension, mediaType) {
var mediaURL = baseURL + extension;
mediaURL = "https://swr-swr3-live.cast.addradio.de/swr/swr3/live/aac/96/stream.aac";
var singleMediaItem = new MediaItem(mediaType, mediaURL);
singleMediaItem.artworkImageURL = "https://d3kle7qwymxpcy.cloudfront.net/images/broadcasts/cd/0c/2275/3/c300.png";
singleMediaItem.description = "description";
singleMediaItem.subtitle = "subtitle";
singleMediaItem.title = "title";
var mediaList = new Playlist();
mediaList.push(singleMediaItem);
var myPlayer = new Player();
myPlayer.playlist = mediaList;
myPlayer.play();
}
It does not show any of the texts an no image. But it used to with tvOS <= 14.0.
Post not yet marked as solved
I encounter the 560557684 (AVAudioSessionErrorCodeCannotInterruptOthers) error too after i stop audio in the other app and send that other app to the background.
Do it this wayset the NSFetchRequestResultType of the NSFetchRequest to NSCountResultTypeexcecute the NSFetchRequest by using the method countForFetchRequest on the NSManagedObjectContextcheck if the returned count is greater than zero
I contacted Apple's developer support and got this answer:"You should be able to submit your app to AppstoreConnect without seeing these warnings. Please submit a complete bug report regarding this issue …"I reverted my changes that tried to fix the initial error messages and my current build did not get warnings anymore.
Post not yet marked as solved
Some 3rd party SDKs do method swizzling "to make it easier to use their SDK" and are causing this issue. Comparehttps://github.com/OneSignal/OneSignal-iOS-SDK/issues/416#issuecomment-423600511I had this with one 3rd party SDK and our project was loading an XIB designable view into a storyboard. Taking the 3rd party SDK out resolved the issue. Or they have to fix their swizzling code.
Post not yet marked as solved
I had this problem too and came up with tow solutions in- (void)userNotificationCenter:(UNUserNotificationCenter *)center
didReceiveNotificationResponse:(UNNotificationResponse *)response
withCompletionHandler:(void (^)(void))completionHandle { …Variant a) Working but using a fixed delay: dispatch_after(dispatch_time(DISPATCH_TIME_NOW, (int64_t)(3 * NSEC_PER_SEC)), dispatch_get_main_queue(), ^{
// handle the UNNotificationResponse
completionHandler();
});Variant b) Working and doing the job as soon as the app is ready: NSBlockOperation *notificationResponseOperation = [NSBlockOperation blockOperationWithBlock:^{
// handle the UNNotificationResponse
completionHandler();
}];
[[NSOperationQueue mainQueue] addOperation:notificationResponseOperation]; Hope you like it :-)
Post not yet marked as solved
I only have seen such controls in 3rd party frameworks that try to shoehorn a Google style feature into iOS segmented control like https://github.com/HeshamMegid/HMSegmentedControlI assume the arrow is sliding to indicate what is selected.Doing this reviews/photos selection control including the sliding green arrow on the green line with a collection view sounds awkward to me. Some kind of animated background for UISegmentedControl would be a more direct way.I really would like to learn how Apple implemented this control in that demo app.
Post not yet marked as solved
This is broken with the tvOS 11.3 betas. I have a bug report for this here: https://bugreport.apple.com/web/?problemID=38170063
Post not yet marked as solved
I got an answer from Adjust saying:yes it is possible with the Adjust SDK to attribute installs to the source which drove that install.By setting up campaign parameter structure to the tracker URL, you can actually find out the the Network Name, Campaign Name, Adgroup Name and Creative Name.For your reference here is the guide to setup campaign parameter structures ->https://docs.adjust.com/en/tracker-generation/#planning-your-tracker-structure
Post not yet marked as solved
It looks like Adjust can do this:Adjust says it uses fingerprinting when IDFA is not availablehttps://docs.adjust.com/en/getting-started/#tracking-installsAccording to https://docs.adjust.com/en/callbacks/#best-practice-accessing-adjust-attribution-data-externallyandhttps://partners.adjust.com/placeholders/the Adjust SDK seems to allow the app access to its data including campaign name for installs.I will comment later if this really worked.
