I have JAR application ready.
i have apple account also. Please give me steps to signed app upload
Distribute apps in the MACOS App Store
This is the general workflow for publishing an app to the App Store using App Store Connect:
Step 1: Choose your build:
Each app can have multiple versions, and each version can have multiple builds. To publish your app on the App Store, choose which build to submit to review.
Step 2: Set pricing and availability:
You must set a price and set a tax category for your app. Although your app is available in all App Stores and localizations by default, you can select specific regions for your app instead. You also have the option to publish your app as a pre-order.
Step 3: Submit your app for review:
You submit your app for review to start the App Review process and to make your app available on the App Store. Before you submit an app, enter all the required metadata and choose if you want to release your app manually or automatically, or if you want to release your app in phases.
Step 4: Request promo codes:
After your app is approved, you can request promo codes to distribute to users before you make your app available on the App Store. You can distribute the promo codes by email or other means, and the user enters the promo code when purchasing the app.
Step 5: View your app status and resolve review issues:
After you submit the app, the app status changes to Waiting for Review. If there are any issues with your app, read and reply to App Review communications. After your app is approved, it can take up to 24 hours to go live on the App Store.
Outside the Mac App Store
While the Mac App Store is the safest place for users to get software for their Mac, you may choose to distribute your Mac apps in other ways. Gatekeeper on macOS helps protect users from downloading and installing malicious software by checking for a Developer ID certificate. Make sure to test your apps with the latest version of macOS and sign your apps, plug-ins, or installer packages to let Gatekeeper know they’re safe to install.
In the comments there are a few useful links (reputation doesn't allowed me to put them here). ;-)
Related
I started to distribute application by Firebase App Distribution using AppBundle instead of APK. But when testers are trying to download build from "App Tester" application it opens Play Store but it opens "Internal beta" page, not Internal App sharing page with this build. Clearing data of Play Store application helps and they see correct Internal App Sharing page with correct build, but only once, when they are trying to download another build it opens "Internal beta" page and they need to clear data again.
I checked on my phones, on two test devices where I have only one authorised account in Play Store, everything works fine. But on my personal device where I have two account I see this issue. Testers have only one account on device but also have this issue, so I don't thing that the problem with amount of accounts.
Has anyone had this issue before and can help me resolve it?
We are develop an iOS app using react-native. And every time there is an update from developer, developer need to build and install on QA phone for testing.
Now, I am trying to use fastlane and firebase app distribution, to distribute new app for QA.
When I create new release, QA got an email notification about that, and they can check it on firebase app distribution. But there is no button for download and install, only message like this.
Device registered!
The developer now needs to update their app to run on your device. You'll get an email when the app is ready to test.
How to make it available to download?
Finally,
For release iOS app to firebase app distribution, you need to generate ad-hoc.
First, u need to create a profiles ad hoc key, u can create it on apple developer or use fastlane to generate it. Then save it inside your project.
Second, set export method inside build app to be ad-hoc.
Third, use get_provisioning_profile to get your profile ad hoc key.
I believe this is very likely because your version is already the same (I think it happened to me recently). Try updating your minor version of the app. (If you are not able to do this for some reason, you can just delete existing build and upload a new one).
I'm using Firebase dynamic links for referrals in an Expo app (managed workflow), but the link data isn't surviving the app installation process. The links worked fine when testing with a standalone app: when the user didn't have the app, they got directed to the App Store/Play Store* and when they did have the app, the link was handled using Expo's Linking.getInitialUrl().
I've actually gone ahead and published a native binary that displays a modal with the link data upon signing up to the app** (again, using Linking.getInitialUrl()). The modal only displays the app's custom url scheme myapp://. This same test displayed the link as expected when testing with a standalone app.
Note that the links work as expected if the app is already installed.
*This answer seems to suggest that this is enough to ensure the data will pass
**Fortunately we are very early stage with no users lol
I am working on one side project, it has image view where a user can click and select an image from the photo library. I am using UIImagePickerController.
My question is I haven't added user Permission on plist nor anywhere else. and as far I know app crashed if you don't add permission, Plus when the app opens for the first time the dialog appears asking for permission but in my case, it's not asking.
I like to know how this can be possible or does Apple have changed something in new Xcode or OS?
I am using Version 9.2 (9C40b) and tried running the code on iPhone 6(real device iOS 11.2.6,) and in different simulator same result, I deleted the app and run it again, same no dialog.
And if Apple has changed something in iOS 11, Should we add or not the permission? whats the best way to a developer we don't want to ask, and also don't want the app to be crashed.
The answer is YES you have to provide the description
It is mandatory to add usage description(from iOS 11) of permissions you are going to use.
Apple states that
Your app is responsible for all usage of privacy-sensitive data, including access to this data by all third-party libraries used in your app. If your app attempts to access privacy-sensitive data without a usage description, your app will exit.
You will see this error in console log if permission description is not provided in Info.plist
This app has crashed because it attempted to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSCameraUsageDescription key with a string value explaining to the user how the app uses this data.
If you try to submit the app without description for release Apple will reject it with this message
Missing Info.plist key - This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSSpeechRecognitionUsageDescription key with a string value explaining to the user how the app uses this data.
Summary:
If you have not provided usage description and uploaded the app earlier then your app will crash without asking for permission
If you have not provided usage description and tried to submit recently then apple will reject it.
Reference:
Privacy Settings in iOS 10
I haven't really used the archive function under Xcode 3, but got used to it now in Xcode 4. So far I always used to have three or four build settings in all my projects: Debug, Distribution AdHoc and Distribution AppStore. Distr. AdHoc and AppStore were both copies of "Release" and only differed in regard to their provisioning profile selected for Codesigning (so essentially they were a thing of convenience, making sure I never sent the wrong person the wrongly signed build).
Now I noticed that Xcode asks me with which profile I would like to sign my build with whenever I export an archived build form the organizer, yet at the same time the build would also fail if the selected provisioning profile in the build settings was not valid. Are Xcode 4 archives provisioning profile independent from or are thy tied to a provisioning profile? How do you solve the "challenge" of having to build for AdHoc and AppStore without having too many build settings groups (switching the groups associated with the build schemes has become somewhat cumbersome in Xcode 4)?
Thanks!
in Xcode 4 if you archive an application it is signed with the provision profile that you have indicated to use under its build configuration. Most likely a settings that was carried over from an Xcode 3 project.
An archived app can be resigned with a different provision profile at a later time (though the organizer or command line), so in a way, yes they are independent of provision profile.
Two suggestions for managing building for AdHoc and AppStore:
1)
The first is taking advantage of Xcode 4 schemes, and creating a new schemes for AdHoc and AppStore
Under the Schemes Menu: Edit Scheme -> Duplicate Scheme, then under the Archive you can select your desired build configuration (AdHoc, AppStore, etc...), you can then name this scheme AdHoc, AppStore to match too. When you want to build for release just select the target scheme and it will sign it with the associated provision profile from the build configuration.
2)
Maintain 1 scheme, remove code signing from your build configurations, and code sign apps exclusively though the organizer after archiving.