To publish an IPA
I go to publish -> Distribute ad hoc/enterprise -> and then I publish the app
However, I can only publish an IPA with a distribution profile, this means I don't get any debugging on my phone.
How can I publish distributed profiles on test flight?
Solved it.
For ANYONE having this problem (i.e. being able to use a development certificate instead of production), follow the following steps.
---- Downgrade your ITunes VERSION to 11.1.5, otherwise it will complain when you try to do an iTunes sync that iTunes doesn't have enough memory!! (Titanium need to fix this!)
1) Download 11.1.5 from here http://mac.filehorse.com/download-itunes/4050/
2) Go to Applications, and Delete itunes... If you get an error message saying something like "This app is require by OSX" just go to Get Info > Sharing & Permissions > Everyone ... it has to say Read & Write.
3) Install the itunes you just downloaded
4) Open it (You might need to hold you "alt" key while opening so you can create a new library (11.2 changed something in your library that is not compatible with 11.1.5)
Then publish app USING ITUNES SYNC. (this is the ONLY way to get the development .IPA)
The app will now be in your app folder within iTunes.
You will now be able to upload your app onto test flight - a development version using a development APNS certificate. Also because it is in development mode, means that you will be able to see all error problems either through Xcode or Iphone configuration. If you publish an ad-hoc system based on production, it will not print out any Ti.App.Info etc commands in the device console.
Hope this helps! :)
Related
my apk is 1.4MB but error is "This APK results in unused code and resources being sent to users. Your app could be smaller if you used the Android App Bundle. By not optimizing your app for device configurations, your app is larger to download and install on users' devices than it needs to be. Larger apps see lower install success rates and take up storage on users' devices."
how to fix this error
It's only a warning, not an error.
For an app that small I wouldn't worry.
It's not something that's made its way into the Ionic ecosystem yet but I heard that if you open up your project in Android Studio and then do the build through there you can create an app bundle.
I'm not totally sure that its fully tested for Ionic so you might have issues with this, but Android have published a full guide:
https://developer.android.com/guide/app-bundle#get_started
This is what they say:
Download Android Studio 3.2 or higher—it's the easiest way
to add dynamic feature modules and build app bundles.
Add support for Dynamic Delivery
by including a base module, organizing code and resources for configuration
APKs, and, optionally, adding dynamic feature modules.
Build an Android App Bundle using Android Studio.
If you're not using the IDE, you can instead build an app bundle from the
command line.
Test your Android App Bundle by using it to generate APKs that
you deploy to a device.
Enroll into app signing by Google Play.
Otherwise, you can't upload your app bundle to the Play Console.
Publish your app bundle to Google Play.
Downloading beta app from testflight app gives error at the end, says "Unable to download app at this time" on all my devices.
No error is in itune connect upload. App displayed and received notification on adding new app to testflight beta. But everytime same error.
This happened to me when I wasn't using the correct provisioning profile. Very frustrating error that doesn't provide any useful info, and leaves the previous installed version of your test build in a state where it cannot be launched. After I switched my provisioning profile to 'Automatic', bumped the build number, and submitted a new version to iTunes connect I was able to download the new build.
I'm seeing a similar error. I don't know for sure, but I suspect doing things in this order may have something to do with it (this seems to mirror what emrys57 is facing).
You have issued a previous TestFlight release (download/install was working).
You then submitted that version for formal review for publication in the App Store.
While the app submission is still under review, now you uploaded a new TestFlight build with an updated version number (but did not resubmit for App Store review).
It could be that while the app is under review something prevents the download. I seem to recall reading about something like this in one of the guides, but I can't remember where off the top of my head. In my case, as an internal tester I even face the error "Unable to download app at this time", regardless of whether I already have a previous version with the same bundle ID already installed or if I don't have the app already installed (i.e., it's fully uninstalled). I wonder if an accepted App Store review will clear up the issue; it doesn't seem like a good idea to resubmit that latest build for further App Store review if the version previously submitted is what you actually want released.
In my case, for the general testing audience, I have a separate bundle ID that is exclusively for beta testing. And that version is never submitted for App Store review (the one that's slated for App Store review I only use for the purpose of smoketesting the upgrade process with internal testers). That bundle ID for beta had to go through the one-time full TestFlight external review for the initial TestFlight external beta testing. But I've been able to keep adding new versions to that beta-only bundle ID for subsequent TestFlight releases without an issue.
I'm using the new beta version functionality in iTunes Connect. I uploaded a build (98) to iTunes Connect, set up some internal testers and they downloaded that build.
Now I've updated the build with a new version (build 99) and that's been uploaded to iTunes Connect, but I can't see how to provoke the system into pushing this new version out to the users and their TestFlight app.
I'm set up as a tester on a couple of devices (both with my developer ID as well as with another id) and I can still only see build 98.
On the iTunes Connect screen build 98 is listed as inactive (which is correct because it has been superseded by build 99), but build 99 only says 'invite testers', but I've invited all those I want to invite.
It says that users will 'automatically receive new builds', but how long does it take? I was hoping it would be instant. Is there a way to provoke iTunes Connect into sending out the update notifications so my users can test the new version?
I'm not sure if this is a bug in TestFlight but toggle off and then on again the "TestFlight Beta Testing" switch. As soon as you do it all your internal testers should get notified of the new build.
Another option is to simply go into the new Build Details and save it.
First off let me be clear. I have several iOS devices. On the devices that have 7.0.6 I have no issues. When I updated one of the devices to 7.1 I'm having an issue. Let me explain.
On the iOS device that has 7.1 I navigate to the workbench URL and then I go to Manage applications and select install. I then get this message "Cannot install applications because the certificate for >ip address< is not vald. This process works on devices that have 7.0.6. I'm assuming there are issues with the new iOS update.
Now I did some searching and I found something that said there's an issue when trying to download an app from a HTTP site, so I changed a Web Reports setting (found in Eclipse Preferences -> Test -> Performance Test Reports -> Web Reports) to "Security is required to access reports". Thus it changed the port number to "8443". I then navigate back to the workbench URL using the https : // ip:port and try to install the app again. This time it just says Cannot open.
Any ideas on this?
Here is a workaround to be able to test with iOS 7.1
1) Get the zip of instrumented Application from developer or other who can run rtwBuildXcode.sh on a Mac and who has the source code for Application. [RmotXXXXXXXX.zip file]
2) Use RTWec "Add Application to list..." button and brows to the zip to "import" it into RTWec.
3) UnZip the zip and use iTunes (for Windows) "Add File to Library..." menu to navigate in zip folder to the instrumented iOS Device application [XXXXXXXX.ipa in “instrumented/iOS Device” folder]
4) Plug in iDevice to Windows using USB, select the App, click associated "Install" button, then "Sync" iTunes.
5) Now test as usual...
Thanks
MTWW in Worklight 6.1.0.0 and 6.1.0.1 (to be released, soon) does not support iOS 7.1.
Work is under way to provide support in a future release of Worklight.
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