Apple developer: How to generate App Id - app-store-connect

I have a app for mobile that is build using AppPresser plugin of WordPress. To generate apk or ipa file I am using Phonegap Build site that provide facility to upload zip folder with source code and returns the .apk and .ipa files for Android and Apple.
Now, I am getting .apk file properly for Android but to get .ipa file, this phonegap require the apple account integrated with it.
So, to integrate this account I have generated .p12 file and now trying to get provisioning profile file. I am on the page of Register an App ID of apple and get stuck at first field of Name. Please check below image.
First part of name is Team Id and second part is Bundle ID. I have googled and checked many docs. Found how to get bundle Id. It can be get from emulator of project on MAC machine.
But my problem is that, I am not developing project through MAC, so how would I get this bundle ID to complete this field with correct value ?
Please help.

You have to add your app name their .
eg :- Whatsapp.
Don't add bundle id in the name of the app.

Related

Update old apk with new

I currently have an app in the play store/app store but recently I started getting problems on my debug version so I decided to create a new react-native project and copy/paste all my code.
Can I build this APK/IPA from this new project and upload it to the store without problems? Will Android/Apple decline my request?
For Android as long as you use the same application id and the same keystore to sign the APK with you can recreate the app and submit it for review to add to store.
For Apple the important part is the bundle id. You need to set the bundle id as same and set the version number to correct one.

iOS new build in Xcode 8 GM not found in iTunesconnection

I can't find my newly uploaded build in iTunesconnect when I click "Select Version to Test" for TestFlight.
When I tried to upload again, my Xcode shows:
But where to find my binary? And how to select the newly uploaded build for beta testing for TestFlight? Thanks.
Earlier I had the same issue and got an email from iTunesConnect pointing out some errors in the build I uploaded. It appears you have to address ALL the warnings (even though those are supposed to be OK for upload) before the build become visible in iTunesConnect.
In my case, I had warnings about alpha channels in my watch app icons.
For why can't you find your newly upload versions:
Check your email.And App Store review my send you an email for lack of user usage description.
Add the key and string value to Info.plist that App Store review ask.
And for why you can't upload your binary file again:
There is a 1.0.20 existed in iTune connect. So you need let your version +1. such as 1.0.21.
And every time you try to upload a new version, you must make your version greater than your latest version in iTune connect.
Then archive and upload it again.
Good luck!

What should I do so I can upload different files for iOS

I had an app in iOS. Now I create another APP and I want to upload the same program as that other APP.
The problem is, how can Xcode knows that this program already points to the new program?
Bundle ID? App ID?
How to identify in xcode that this is the program for what program?
In other words:
How does xcode knows which app belong to the archive?
Is it by bundle id?
If I uploaded an APP and then create another APP in itunes connect, what should I do to do the itunes connect?
Short Answer is Bundle ID.
When you validate or distribute any app from Xcode to iTune it search for Bundle ID in your account and work according to that.
Your provisioning Profile have information about your Bundle ID and App ID. So set proper Bundle ID and provisioning as you do for previous app upload.

Error uploading to Testflight Unexpected Error parsing IPA

I am trying to upload my app to test flight. When I use the web interface, I get the error
Unexpected error parsing the IPA, TestFlight support has been notified.
And when I try to upload using the desktop app, it tells me that dSYM is not found, lets me go through the whole process, then give the same error at the end.
Built in XCode 4.5 for deployment target 5.0.
I have looked at Error Upload TestFlight : Invalid IPA / dSYM not found and as far as I can see, all my build settings are set to armv7.
Is there anything obvious that I should check/could be missing?
The only 2 external libraries in the project are test flight sdk and flurry.
I've had the same problem when trying to upload .ipa files. The problem is, that .ipa files don't contain the symbolication information anymore.
Try exporting your app as Xcode Archive instead of building the .ipa for distribution (thats one of the options when you choose 'Distribute...' in the Xcode organizer). This archive contains the necessary dSYM files (if not, you have to check your build settings). If you drop this .xcarchive into the TestFlight desktop client, TestFlight will build the .ipa for you and the upload it.
Make sure to use the same Provisioning Profiles for signing the .ipa in the TestFlight client that you have used when building the archive in Xcode!
Or you can just choose to Show the TestFlight Co-pilot in the menu bar (activate in the settings), the it will automatically detect your Archive.

Steps in deploying Android App developed using Titanium to Google Play store

I am using Titanium Studio to build my application, i have got it released in app store for iPhone.
But now i am trying to publish this to Google Play store. Below are the steps i am following, please let me know if i am doing wrong
1) Created a Google Publisher account (to get access to Google Play console)
2) Build my application in Titanium Studio, and copied the app.apk file from /build/android/bin directory
3) Uploaded this app.apk file in Google play store
I know i should add more details like appicon, screenshots to the app before publishing it.
But is this the correct procedure? because i can see in some articles suggesting
to create private key to package app.apk file.
Please suggest.
balanv here is the link i have for signing APK for unity: http://answers.unity3d.com/questions/149094/android-apk-signing.html
OR one closer to your problem:
https://wiki.appcelerator.org/display/guides/Packaging+for+the+Android+Market
also look at https://wiki.appcelerator.org/display/guides/Packaging+for+the+Android+Market