Im trying to use beta to distribute with development and distribution provisionals.
Using different schemes.
Im using fastlane.
If i use gym(scheme: 'xxxx', export_method: ‘development’)
The push certificates are dev.
If i use gym(scheme: 'xxxx', export_method: ‘app-store’)
the app appears in the beta page but it says that the distribution is wrong.
If i use any other export_method i get a gym error.
So how do i upload the app with dev/distribution provisionals and cpush certificates?
Thanks
Related
While uploading app on Google playstore, we are getting below error.
You need to use a different package name because [pkg_name] is used by
a pre-installed application. To upload a pre-installed application,
please contact Google Play Developer Support.
I am sure that mentioned pkg name is unique, however we have pre-installed this app in some of devices. Now how to upload it to Play console ?
I got this solved by using contact support team of Google, They then contacted carrier/preload team to allow package.
Sometimes if you preload app first and then publish app on Playstore, Google play will block the package and confirm your identity from pre-load team before allowing you to publish.
So it is advised to put package in store first & then pre-load to avoid such long process. (You can limit discovery via multiple ways).
Source - https://medium.com/#shashank.mishra_62841/complete-guide-in-app-update-for-android-apps-google-playstore-1b8f2946fa7a
I am testing WSO2-Emm system for managing our android mobile app. We have an app for taxi drivers. We deploy it using our tablets and a single gmail account. Our problem is that google allows up to 10 signed in devices for a single google account.
I have tried to load the apk to the WSO2 store. The problem is that when I want to upload a new version of the same app I get a warning message saying that this APK already exists in the store. When I try to rename it and add it as a new apk it works. The problem is that when I go to App-Management, the application appears under 'installed'. The Emm system doesn't detect there is a new version.
To be more specific, my question is is there a way to manage mobile application versions using the WSO2 store and not the google play store.
If there is a way we can go on with this system. If not, we will stop testing it.
The only way I've figured out how update an already installed app is by going to the App Management tab, selecting your latest version of the app in question, and hitting the install button under the Roles tab (NOT the Users tab). It will send the install command to any devices listed under roles you have checked, even if they already have the app installed. Keep in mind this will install the app on all the devices, even devices that already have the version you're trying to put out.
It looks like you already know about the patch on EMM-686 that must be implemented in order to upload multiple versions of the same app to the Publisher. Just in case you want to confirm it's implemented correctly, see my answer here for instructions on how to implement it.
I am trying to upload a build on TestFlight and trying to pass by the step where I have to add developer account to the Xcode preferences. It's partly a good step but I don't like the mess, it creates with certificates and provisioning profiles. Any chance I can either bypass the developer account setup or the provisioning profiles.
Unfortunately there is no way to deploy your app to actual devices without creating certificates and provisioning profiles. This applies to both Development and Ad Hoc/Testflight distribution.
It's one of the necessary evils of iOS development.
I've created an iOS7 project in Xcode 5. It's a very simple app. I zipped it and sent it to another developer. When they open it, they get these messages:
No matching code signing identity found
No code signing identities (i.e.certificate and private key pairs)
matching "iPhone Developer" were found. Xcode can resolve this issue
by downloading a new provisioning profile from the Member Center.
How do they get around this? The app isn't going to be submitted to the app store.
Is this happening because they have not linked Xcode to their online developer account? Isn't an online developer account free?
The other developer can ignore that message if the intention is to run the app on the Simulator. But you must use code signing in order to run an app from Xcode on a device, even for testing purposes, even if the app is never going to be submitted to the App Store. And that costs $99/year. End of story.
You could turn your account into a Company account and put this developer on your company; that way the developer is covered under your $99.
Or, if you just want to send the app to someone for testing and you don't need them to run the app directly from Xcode on a device, you can create an Ad Hoc build targeted to their device.
And of course the developer can look at your code, test on the simulator, and run your previously built Ad Hoc build on the device - but not run from Xcode on the device, i.e. the developer can not build for a device without someone paying that $99/year fee.
I'm in the process of learning iOS development and app submission process. Before trying to archive my application I only tested and debug it on iOS 6 simulator and now I want to deploy this application on real device. And during this I encountered with some problems.So, what steps I must implement in order to successfully archive my application and get an .app and then an .ipa file of it. How to setup provisioning profiles and solve code signing error?
You need to go to the provisioning portal at http://developer.apple.com and generate provisioning profiles for your applications there.
If you have not paid your developer license fee you will not be able to install your apps on real devices.
You will need to get a Developer and or Distribution certificate including their respective Private keys. You will also need a Team Provisioning Profile, or a Provisioning Profile specifically made for the app. You can either make all these yourself through the provisioning portal at http://developer.apple.com Or if you are working for someone else who has a developer program license, they could possibly provide you with all these.
The provisioning profile describes all the steps you need to take to implement the certificates and provisioning profiles so you can build and deploy / distribute your app.