[PHCollectionList isPrivacySensitiveAlbum]: unrecognized selector crash

Question

Created Apr ’23

Replies 1

Boosts 0

Participants 1

I cannot find anything documentation re: isPrivacySensitiveAlbum. I've granted my app access to all photos. Not sure what else to try

Code that triggers the crash:

    let options = PHFetchOptions()
    options.fetchLimit = 1
    
    let assetColl = PHAssetCollection.fetchAssetCollections(withLocalIdentifiers: [localId], options: options)
    
    if assetColl.count > 0 {
        if let asset = PHAsset.fetchKeyAssets(in: assetColl.firstObject!, options: options)

stack trace from here on

`2023-04-15 06:34:41.628537-0700 DPF[33615:6484880] -[PHCollectionList isPrivacySensitiveAlbum]: unrecognized selector sent to instance 0x7ff09232aec0
2023-04-15 06:34:41.632378-0700 DPF[33615:6484880] *** Terminating app due to uncaught exception &#039;NSInvalidArgumentException&#039;, reason: &#039;-[PHCollectionList isPrivacySensitiveAlbum]: unrecognized selector sent to instance 0x7ff09232aec0&#039;
*** First throw call stack:

(

	0   CoreFoundation                      0x00007ff80045478b __exceptionPreprocess + 242

	1   libobjc.A.dylib                     0x00007ff80004db73 objc_exception_throw + 48
	2   CoreFoundation                      0x00007ff8004638c4 +[NSObject(NSObject) instanceMethodSignatureForSelector:] + 0
	3   CoreFoundation                      0x00007ff800458c66 ___forwarding___ + 1443
	4   CoreFoundation                      0x00007ff80045ae08 _CF_forwarding_prep_0 + 120
	5   Photos                              0x00007ff80b8480e1 +[PHAsset fetchKeyAssetsInAssetCollection:options:] + 86
	6   DPF                                 0x0000000100791029 $s3DPF16AlbumListFetcherV22loadKeyImageForLocalIdySo7UIImageCSgSSYaFTY0_ + 569`

Boost

Answer 1

LeeInCA OP

Apr ’23

I did notice that the localIdentifier of the asset that causes the crash ends in "020" where as everything else ends in "040". And the album in question is actually a folder of folders. But I can't find a way to work around it other than checking the localIdentifier. Brittle to the say the least.

0