App Review doesn’t care about why an app is using private API, it’s a hard and fast rule (at least in theory).Īt a surface level, it seems like it should be relatively straightforward for Electron to remove the API references and use alternative approaches. It does not appear that Electron is doing anything extreme, certainly nothing malicious. Individual Electron app makers are a bit helpless as the issue can only really be fixed by pushing changes in the Electron code itself. What has happened is that Apple has upgraded its server-side app review processes to detect more violations of its App Review guidelines, and now this private API usage is being identified. The detected private API symbols include:Īpparently, the Electron framework has used these APIs for years. These API calls are not in the app itself, but part of the underlying Electron framework. The apps in question are getting flagged because of their usage of private API calls. This means app rejection policies on macOS are not as painful as with iPhone or iPad, but they are nevertheless significant.ĭevelopers are reporting that apps made using Electron (which is a framework that allows companies to ship web apps in a native app wrapper) are now being rejected by the automated Mac App Store review process. On macOS, the Mac App Store is just one method of distribution and developers are free to publish their apps independently on their own website. Your Electron App will be opened and you can check console output for errors.On iOS, all apps must go through the App Store. $ electron -debug= "4444" electron/dist/QuasarElectronApp-linux-圆4/QuasarElectronApp So how can you debug this? Simple: $ electron -debug= path/to/production/executable But what happens when the production build has something failing? It may happen, for example, that if you made a mistake in the code in some scenarios you’ll only see a blank window showing up. While developing you got Chrome Dev Tools available. └── package.json # npm scripts and dependencies for Electron ├── dist # where production build will go If you want to only build for a specific platform, like Linux, simply add another parameter to quasar build: Make sure you build Quasar app from root project folder before packaging it with Electron and then follow these steps: # from Electron wrapper folder: # Make sure you keep running (from root project folder): As a bonus, besides Hot Reload, the Chrome Dev Tools will also be available so you can easily inspect code. The wrapper will open an Electron app which will point to your App. You can benefit from Hot Reload while developing an Electron app. Next, change current directory to the newly created /electron folder and npm install its dependencies: $ cd electron It contains the assets of an Electron project mapped to your Quasar App. This command generates a subfolder inside your App named /electron. Now let’s create the Wrapper for your App. Won’t work with any other specific starter kits, like “pwa”. The Quasar Electron wrapper can be installed on top of the default starter kit. We’ll be using Quasar CLI to manage this. You can build Electron apps by wrapping your Quasar project with its Electron wrapper.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |