1) I'm achieving the build using Xcode 6.3.
2) After Successful validation submitting the build to app store for beta testing.
Xcode is showing the status "submitted successfully".
The issues is, The build is not visible in itunesconnect under prerelease tab.
I checked the version. Version number in not same. Any suggestions are highly appreciated. Is there any issue with Xcode 6.3 or iTunesconnect.
I was facing the same problem. I just uploaded the binary again and now it showed up in prerelease.
Related
I've got codepush working for a staging build of an app I hope to soon have in production.
On initial download from the app store, the fonts are looking great! My version checking info that I have in the app shows me that I'm using the bundled version of the bundle.js
If I force-quit and re-launch the app (causing an update) the fonts are no longer found in the application. They display the "missing glyph" image (see screenshot below).
I'm hoping for either a solution, some tricks to try, or just some ideas about how to further debug and understand what is causing this. I'm a little stuck because when I try to run the app in debug mode, it just uses the latest codepush version instead of downloading a new one.
I am using Application Loader to upload my .ipa files (created with Adobe AIR v18) to iTunesConnect.
It's been working fine for months, but today I received two new errors:
The u option must have a non-empty value.
The password must have a non-empty value.
Can anyone shed some light on the issue?
I upgraded to Xcode 7.1 and that solved the problem!
Note: Xcode 7.1 comes with Application Loader 3.3.
You have 2 solutions:
1) Update your Xcode to 7.1 (but since you are not coding natively, use the solution #2 below)
or
2) Download and use the Application Loader v3.1 (Download link: https://itunespartner.apple.com/en/apps/tools ) to submit your IPA
Apart from low-belly's answer you can try to use XCode's built-in upload feature. If you go to the Organizer, just click on Upload to App Store:
This solved the problem for me in XCode 7.0.1.
Xcode 7.1 was downloading too slow (more than 4GB) and the update failed every time, so for now I downloaded the Application Loader 3.1 from iTunes Connect and it worked fine.
To download it you login into iTunes Connect -> Resources and Help -> click on View Tools (under the title Other Resources at the bottom of the page) and there is the download link.
I got the same error last night. Fixed it by signing out of Application Loader (3.6) and logging back in.
I got the same error with Application Loader 3.2. Submitting with Application Loader 3.0 (bundled with Xcode 6.2) or 3.1 (bundled with Xcode 6.4) solved the problem.
The content assistant is not working.
I'm working on OSX, Titanium Studio, iOS & Android mobile app and have tried the following:
Installing the following SDKs: 3.2.0, 3.2.1, 3.3.0.
Tried reverting between those versions.
Checked the Project Natures (mobile - primary, mobile module, are checked).
Tried every option on the Project Build Path.
Of course tried to build the project again and again.
Check the content assistant preference both in the main preference and in the project properties.
Are the any more suggestions?
I believe this is a bug in the 3.2.0GA SDK (3.2.1 and 3.3.0 are not official releases yet). As far as I have heard it is known and should be fixed in the next SDK update. Only question is when this update will be out.
You can get content assist back by reverting to 3.1.3GA, but that doesn't help you much if you need features from 3.2.0GA.
EDIT:
The issue is described in this JIRA-ticket and as it mentions should be resolved in the upcoming 3.2.1 release.
I've installed Testflight (1.2 B3) as stated in the documentation. Builds are uploading and updating fine. I can see sessions (mostly anonymous :/), I receive the logs (TFLog) - but I do not receive any crash reports. I even introduced a crash-on-event (a method not found thing) - but theres is nothing on Testflight about it.
Provisioning is via a developer profile which embeds several devices.
The problem occurs on iOS6 and iOS5 / iPhone5 and iPad3. The is being build against iOS6.
Any ideas?
UPDATE
I've tested several other frameworks and ways to receive crash reports. Nothing worked so I suspect something in my code (obviously). Are there any other switches that XCode 4.5.1 might have enabled and that way disable any error reporting during a "production environment" like setup?
UPDATE 2
As of now we're using Testflight only for distribution of beta versions and switched to Crashlytics for crash reporting. It's a bit more streamlined and fetches most crashes.
I also do not get any crash reports via TestFlight. This is what the TestFlight people told me:
Our team is currently looking into an issue associated with auto
versioning of the app when uploaded and SDK data not reporting
properly. Looking at the URL you provided it looks like the build
version is not changing before uploading the app to TestFlight and our
auto versioning implementation is causing an issue with general SDK
data reporting.
I will share this with our team and we will contact you when we have
an update available.
I tried to update the build version to avoid auto-versioning, but it did not help me. But maybe this issue is hitting someone else.
Testflight did not satisfy our needs to log crashes. That is why we skipped to Crashlytics (as I said in the original post). The issues with Testflight seem not to be resolved. We still do use it for distribution, that is what it's good at.
I just upgraded to xCode 4.3 and used it to generate a new revision of an iPad app about 50 beta testers have been using for several months. I distributed the beta app through TestFlight as usual.
Most testers upgraded with no problem, but several testers are getting the TestFlight message "You have not permitted this device to install this build" when they try to install the new rev. I've never seen this message before. Their iPad UDID is definitely in the build's embedded.mobileprovision file and everything was working working fine with the prior revision.
What am I -- or the testers -- doing wrong and how do we correct it?
Hi i experienced the same and it seems that you must generate your mobile provisioner profile from Xcode(instead of Apple dev site for example) and you should update your App permissions (TestFlight) with this same provisioner profile that you just generated on your machine so basically the machine that generates and archive the apps using Xcode must generate the provisioner profile and then you should update your testflight app permissions with this file.
Does that make any sense?
Hope this works for you testflight is really nice to use, i faced same problems with all of my apps and hardware devices (testers all around the world)
Thanks
Turns out this is apparently a bug in Testflight. I tried to resolve the issue through their support forum and multiple emails with no real answer. I did not want to switch services as my testers knew the Testflight system well. But eventually switched to Diawi. My testers were able to install the app using Diawi with no problems.