Safari 10.0: App Extensions should show marketing version number not internal version

Originator:aralbalkan
Number:rdar://28462184 Date Originated:24-Sep-2016 04:22 PM
Status:Open Resolved:
Product:Safari Product Version:Safari 10.0 (12602.1.50.0.8)
Classification:UI/Usability Reproducible:Always
 
Summary:

The internal version number of Better for macOS is 100.0 (don’t ask – we got into a rejection argument with iTunes Connect when I accidentally set the version number to “2” instead of “2.0” and then couldn’t increment the build number back for the 2.0 track… anyway, long story short, after a couple of rejections near midnight, I chose the nuclear option and set the version to 100.0 and the build number to 100 (because, what could possibly go wrong, right?)

As you can see in the screenshot, the internal version number is being presented in the Safari Extensions panel.

Steps to Reproduce:

1. Mess up the version number in your binary and upload it to iTunes Connect (“2” seems to work)
2. Get into a binary rejection back-and-forth with iTunes Connect by trying 2.0 (1), 2.0 (2), 3.0 (1) etc.
3. Get angry
4. Set the version to 100.0 (100)
5. Release the app
6. Look in the Extensions panel in Safari and see Your App 100.0 from Your App as the extension name.
7. *sigh*

Expected Results:

* With the App from the Mac App Store: Safari App Extensions should show the same marketing version that people see in the App Store next to the extension name (e.g., for Better, it should read Better 1.1 from Better)

* When testing with development builds: it’s OK to show the internal version (and probably better as it provides a visual distinction to the extension being tested versus the version installed from the App Store).

Actual Results:

Safari App Extensions downloaded from the Mac App Store show the internal version number (100.0)

Notes:

People using your app should not have to know or care about the internal version and may be confused when the version of the app extension they see in Safari differs from the marketing version that they saw while downloading the app itself. Since these versions cannot be different (or the binary is rejected) it makes sense to show the marketing version. The internal version would still make sense to show when the app is being tested in the debug configuration during development.

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!