question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Deprecated API Usage when submitting to MAS - QuickTime/QTKit APIs

See original GitHub issue
  • I have read the contribution documentation for this project.
  • I agree to follow the code of conduct that this project follows, as appropriate.
  • I have searched the issue tracker for an issue that matches the one I want to file, without success.

Please describe your issue:

After compiling my app using electron-forge package --platform=mas, and submitting my app to the Mac App Store (with intermediary steps), I get the error: "Deprecated API Usage - Apple no longer accepts submissions of apps that use QuickTime or QTKit APIs.

Error Screenshot

I’ve done some snooping around, and some of the only other issues that replicate this are with very old versions of Electron and electron-packager, or with people not using the --platform=mas command properly. However, my version of electron-forge and the created app both use relatively updated versions of each dependency, and I’m using the --platform=mas option.

Has anybody else encountered a problem publishing an Electron-Forge app to the Mac App Store? I’m currently using the Angular 5 boilerplate - my code is available here.

What command line arguments are you passing?

electron-forge package --platform=mas
electron-osx-sign ...
electron-osx-flat

I upload the file outputted by electron-osx-flat, but I’ve identified that the problem is with electron-forge package --platform=mas - the other two commands work on a non-Electron Forge project.

What does your config.forge data in package.json look like?

"config": {
    "forge": {
      "make_targets": {
        "win32": [
          "squirrel"
        ],
        "darwin": [
          "zip"
        ],
        "linux": [
          "deb"
        ]
      },
      "electronPackagerConfig": {
        "packageManager": "npm",
        "icon": "src/assets/img/fair-chair.icns",
        "ignore": ".+.o$",
        "appBundleId": "me.matthewwang.fair-chair",
        "helperBundleId": "me.matthewwang.fair-chair.helper",
        "buildVersion": "1.0.2"
      },
      "electronWinstallerConfig": {
        "name": "fair_chair"
      },
      "electronInstallerDebian": {},
      "github_repository": {
        "owner": "malsf21",
        "name": "fair-chair"
      },
      "windowsStoreConfig": {
        "packageName": "",
        "name": "fairchair"
      }
    }
  }

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:8 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
mattxwangcommented, Apr 4, 2018

@MarshallOfSound @malept I think I figured out the problem, which is quite odd. I did a full reset of my node configuration (so deleting node_modules, reinstalling node and my global packages), and I still encountered the problem - however, I noticed that the electron package was still in my MAS-packaged app’s contents even after removing it with the suggestion from @malept . This should be unexpected behaviour, as I was not installing electron into the app (but it was required by electron/types.

This is problematic because the electron package contains Electron.app, the distributable .app, which is not MAS compliant. Therefore, this is what was triggering the QtKit alert (at least to my knowledge).

So, before signing the app (but after packaging it with electron-forge package --platform=mas), I went into the .app’s package contents, deleted Resources/app/node_modules/electron/dist (which contains the Electron.app), and then proceeded normally. My app was successfully submitted to the MAS.

I’m not entirely sure what’s causing this to happen - I think it’s the requirement of electron from electron/types, which is a non-mas compliant distributable. What do you think?

0reactions
mattxwangcommented, Apr 3, 2018

@MarshallOfSound , any thoughts? Is there somewhere else that I should look for, or another project I should consult?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Deprecated API Usage when submitting to MAS - QuickTime ...
Please describe your issue: After compiling my app using electron-forge package --platform=mas , and submitting my app to the Mac App Store ( ......
Read more >
Deprecated API Usage - Apple no longer accepts submissions ...
I received mail with : Deprecated API Usage - Apple no longer accepts submissions of apps that use QuickTime APIs. source : https://developer.apple.com/ ......
Read more >
ITMS-90809: Deprecated API Usage - Apple Developer
ITMS-90809: Deprecated API Usage - Apple will stop accepting submissions of apps that use UIWebView APIs.
Read more >
Uses deprecated APIs - Chrome Developers
Lighthouse audit shows usage of deprecated APIs. Lighthouse includes all deprecated API warnings that Chrome logs to the DevTools Console.
Read more >
Rejected when submit to Mac App Store. Because ITMS ...
ITMS-90300 : Deprecated API Usage** - Apple will stop accepting submissions of apps that use QuickTime or QTKit APIs .
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found