LSHandlerRank key (again)

Hello,

first things first: this post is not a rant; the idea is to alert people who may run into this problem and like me are not very proficient in handling .plist etc.

So, today I tried to upload to MAS two apps of mine, but for both of them, and the end of the process, App Loader showed the warning at the bottom.

From a previous post, I knew that I had to set the Rank in App Wrapper, but this time I could not, because in the case of the .wav filetype, the filetype entry was shown at the bottom of the window (of App Wrapper), where there is no Rank menu.
While in the second case, the Xojo filetype was “special/any”, and in App Wrapper did not show anywhere.

What makes the two issues similar, is that:

  1. in Xojo > Inspector, both filetypes are ticked/checked and labelled “None”;
  2. in Xojo filetype set, both do not have an icon and they are set as “Imported”.
    (I guess App Wrapper could not fix the issue because the Rank popupmenu shows up only if there is an icon. But I’m not sure about it. On the other end, I may be wrong, but I guess a lot of us do not put icons to common imported filetypes like “anyfile”; Xojo itself does not provide icons when choosing a filetype).

Meantime I solved the issue adding in the info.plist created by Xojo the necessary Rank, just below the Role entry:

CFBundleTypeRole
None
LSHandlerRank
Default

Then I wrapped the apps and App Loader did not complain anymore.

But I ask myself if Xojo itself could not create a .plist with the Rank entry. In this way it would not be necessary for us and for Sam to fix the matter manually.
Unless I did something very dumb that should be avoided/corrected/

[quote]Dear Developer,

We identified one or more issues with a recent delivery for your app, “xxxxxxx” 1.1.7 (49). Your delivery was successful, but you may wish to correct the following issues in your next delivery:

ITMS-90788: Incomplete Document Type Configuration - The CFBundleDocumentTypes dictionary array in the ‘xxxxxxx’ Info.plist should contain an LSHandlerRank value for the CFBundleTypeName ‘audio/wav’ entry. Refer to https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html#//apple_ref/doc/uid/TP40009249-SW1 for more information on the LSHandlerRank key.

After you’ve corrected the issues, you can use Xcode or Application Loader to upload a new binary to App Store Connect.[/quote]

[quote=447033:@Carlo Rubini]Hello,

first things first: this post is not a rant; the idea is to alert people who may run into this problem and like me are not very proficient in handling .plist etc.

So, today I tried to upload to MAS two apps of mine, but for both of them, and the end of the process, App Loader showed the warning at the bottom.

From a previous post, I knew that I had to set the Rank in App Wrapper, but this time I could not, because in the case of the .wav filetype, the filetype entry was shown at the bottom of the window (of App Wrapper), where there is no Rank menu.
While in the second case, the Xojo filetype was “special/any”, and in App Wrapper did not show anywhere.

What makes the two issues similar, is that:

  1. in Xojo > Inspector, both filetypes are ticked/checked and labelled “None”;
  2. in Xojo filetype set, both do not have an icon and they are set as “Imported”.
    (I guess App Wrapper could not fix the issue because the Rank popupmenu shows up only if there is an icon. But I’m not sure about it. On the other end, I may be wrong, but I guess a lot of us do not put icons to common imported filetypes like “anyfile”; Xojo itself does not provide icons when choosing a filetype).

Meantime I solved the issue adding in the info.plist created by Xojo the necessary Rank, just below the Role entry:

CFBundleTypeRole
None
LSHandlerRank
Default

Then I wrapped the apps and App Loader did not complain anymore.

But I ask myself if Xojo itself could not create a .plist with the Rank entry. In this way it would not be necessary for us and for Sam to fix the matter manually.
Unless I did something very dumb that should be avoided/corrected/[/quote]
This has been fixed in a future version of Xojo.

Good news indeed.

Thank you Greg & Xojo.

Thanks for the upcoming fix.

As usual, this is a new requirement that needs to be added.