I've misunderstood how projects work in AppGallery Connect - and uploaded 4 different apps to the same project (they have all been published for a while). Is it possible to move apps to a new project? There is an option to transfer apps, but that is to move the app to a whole new account.
Related
I am making an app with Unity and i prepared the app for release on Google Play (key and other settings)
But for some reason it doesn't let me upload .apk, only .aab. Last time i published a game (3 months ago) it worked with an .apk but for some reason it won't work now. Did miss something?
By new google policy, From August 2021, the Google Play Console will require all new apps to Publish with the Android App Bundle format so, Your build must be as aab. in unity for build as aab you must check Build App Bundle (Google Play) in Build Settings.
also for more detailed how to sign with previous sign key and setup aab see:
https://blog.unity.com/technology/support-for-android-app-bundle-aab-in-unity-2018-3-beta
https://developer.android.com/studio/publish/app-signing
https://forum.unity.com/threads/android-app-bundle-google-play-app-signing-what-option-do-we-use-with-unity.604723/
https://forum.unity.com/threads/android-app-signing-by-google.471539/#post-4618345
I'm trying to deploy are beta-testing app to google play as a production mode. We are able to deploy as a beta testing last week, and after that I added lot's of change to our code. Finally I finished writing code for the app now, and thinking to deploy the app as production on google play. I was wondering, if I should update the Android App Bundle on Beta section in app releases then hit "release to production" button (on Beta section page in app releases), or I should go to Production track and drop the new Android App Bundle. Does it really matter?
It doesn't really matters, tho, if you create a new appbundle and deploy it in production mode, you should after that disable your beta bundle, otherwise users that have access to beta will see two apps in the Play Store.
So I'm developing one application with Ionic 3 and we had some problems to test push notifications and generate one test version for iOS users.
Recently Ionic View was removed from Apple store, and same with the Ionic View in the apple store we had some problems to test push notifications, I know that Apple has TestFlight and we think that we can use TestFlight for our iOS users but I don't have one mac but I have Ionic Pro.
My doubt is that "Can I use Ionic Pro to generate one version to use in TestFlight without one MacOS?"
You can use Ionic Pro to do most of what you're looking for, EXCEPT creating the proper .p12 certificate file. As far as I know, you must use a Mac for that. Fortunately, that's a one-time process, so you can perform other aspects of the build process within Ionic Pro.
So, basically you need to create your .p12 certification file on a mac, and
upload it to Ionic Pro -> Settings -> Certificates. You can then build .ipa files with proper credentials in the cloud. Then... you have to upload the ipa file to the app store, and distribute it via TestFlight there.
Another option: There is a pay-as-you-go Mac cloud account service (https://www.macincloud.com/) that might be perfect for what you're doing, specifically since you either only need to create the certificates (at best) or you'd only have to use it when you were creating builds and uploading them via XCode Application Loader. (at worst) Perhaps that's something that you might want to explore? I will say, it is much easier doing that kind of development directly from within a Mac environment, unfortunately.
i'm trying to find a way to publish an app to cydia other than app store from titanium appcelarator so i can test the app before registration for the developer program.
are there any clear steps to build and publish the app to cydia and to the app store?
If you go into the build/iphone folder within your project you'll find the XCode project for the app generated by Appcelerator. You can open this into XCode and build the app in the same way you would any app for distribution to cydia.
If you are just after beta testing however, check out http://www.testflightapp.com/ it allows you to distribute and manage beta testing over the air and is all legit.
I've had a query about developing an app for members of an association and I can't determine from the Enterprise Deployment guide if this is an appropriate method for deploying the app.
Members own their own devices, so can an enterprise app be deployed while allowing the users to continue to use their own Appstore logins?
At any point, do the devices have to be physically connected to a machine running iTunes that is owned by the association or can a provisioning profile be distributed via the web or email? I see that profiles found in certain directories (e.g., ~/Library/MobileDevice/Provisioning Profiles/) will be automatically installed, so can the profiles and the app simply be emailed to members?
The Enterprise Deployment guide contains a lot of instructions on locking down the device. Can this be ignored?
I've had a query about developing an app for members of an association and
I can't determine from the Enterprise
Deployment guide if this is an
appropriate method for deploying the
app.
Sounds right for the type of deployment you're talking about. Just be aware if you're have the enterprise developer account you won't be able to do App store deployment with the same account.
Members own their own devices, so can
an enterprise app be deployed while
allowing the users to continue to use
their own Appstore logins?
Yes, Appstore apps and enterprise apps can coexist on the same device.
At any point, do the devices have to
be physically connected to a machine
running iTunes that is owned by the
association or can a provisioning
profile be distributed via the web or
email? I see that profiles found in
certain directories (e.g.,
~/Library/MobileDevice/Provisioning
Profiles/) will be automatically
installed, so can the profiles and the
app simply be emailed to members?
You can get the app binary and profile to the members anyway you like. Snailmail a CD... stick a USB drive on a pigeon... As long as they have access to the iTunes they sync their devices with, they'll be able to install your app.
The Enterprise Deployment guide
contains a lot of instructions on
locking down the device. Can this be
ignored?
Not sure which guide you're referring to. Please include link.
You need the devices UDID which is included in the provisioning profile for the app, that allows that device to run the app