When adding the Distriqt Share ANE to my app via Flash Pro CC 2015 I get an Invalid input error and the app will not publish.
This is simply adding the ANE to the Library Paths list, no import or AS3 code is added.
If I remove the ANE, the app published fine. I have checked that the dev key is correct and compatible with the Share ANE.
Would anyone have any idea why this is happening and what can be done to fix it?
Thanks,
Mark
I had this same issue and found you need to include the iOS sdk when compiling to get past in invalid input error.
Instructions here: http://airnativeextensions.com/knowledgebase/tutorial/1#ios
Related
I'm getting this error when opening VS Code. Does anyone know what it means? I've done some research but didn't get any relevant information :(
I've tried creating a workflow to see if the error disappeared, but it didn't.
It seems that react native is asking for a workspace to start but is it asking that in the first place? Can I disable react native from running when opening VS Code?
The folder opened when the screenshot above was taken was the folder it opens by default, I believe it's the mac "home" personal folder, and I have a folder called "git" inside of it, with all projects.
Given the date of this posting (2023-02-07), you're probably on version 1.10.0 of the extension. This sounds like this bug report in the microsoft/vscode-react-native GitHub repo: [Bug] Extension activating when it shouldn't #1891.
A fix is coming in version 1.10.1.
But it is taking some time and has not been release yet at the time of this writing 2023-01-31:
we're facing some problems in the last release process, recently we're waiting for new publishing PAT access to republish 1.10.1 again, maybe it will publish on marketplace on next week. We have nightly version for extension in marketplace as well, maybe you can use it now.
For now, you can try installing the nightly version.
Also, note from the extension's readme documentation:
Before going any further make sure that you:
have a working React Native environment.
have the emulator utility available in your PATH if you're developing Android applications.
[...]
Got it, this annoying log came from React Native Tools extension. They specify the requirements in the docs:
In my case, I don't have a specific React Native environment or the emulator PATH is not right.
I am trying to upload my app to the app store. I can archive my app and successfully upload to App Store Connect, however, it keeps getting rejected with the following error message:
Dear Developer,
We identified one or more issues with a recent delivery for your app, "Retainer Tracker" 1.0 >>(8). Please correct the following issues, then upload again.
ITMS-90424: Invalid Swift Support - The SwiftSupport folder is empty. Rebuild your app using the current public (GM) version of Xcode and resubmit it.
Best regards,
The App Store Team
I've tried a bunch of diffrent fixes I've found online but still can't get it to work. Can anyone help?
The basic reason is your application using swift and your swiftsupport folder is empty. Let's move in detail
If your application using Xcode to make .ipa file and there is no third-party IDE involve to create Xcode project, you can fix this issue by upgrading your Xcode
If you are using some other IDE to make the Xcode project then please follow that link. I already give the answer to this question. Invalid Swift Support - The SwiftSupport folder is empty
The problem occurred right after I added a specific Swift Library
Doing the following fixed the issue in my case
Go to Targets > YourApp > Build Settings
Under Packaging:
Defines Module: Yes
Under Assets:
Always Embed Swift Standard Libraries: Yes
ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it.
For us, our CICD pipeline was using an Ad-Hoc Provisioning Profile to distribute the ipa build to Testflight/AppStore.
We fixed this by using an App-Store Provisioning Profile instead.
I trying to use the Titanium Healthkit module in Appcelerator Labs and I am getting an error. I am using Ti SDK 5.2.0
HKHealthStore: failed to determine authorization status: Error Domain=com.apple.healthkit Code=4 "Missing com.apple.developer.healthkit entitlement."
I have been reading through the posts on the old forum, and this seems to be a common error. https://archive.appcelerator.com/topic/1596/apple-healthkit-integration/11
Is there any new or updated info? I am reluctant to patch the SDK, because I don't know if it is still valid or what it will do.
On the Labs page it says:
You will also need to add HealthKit to the app’s list of entitlements. See the Entitlements.plist file in the example folder.
Did you add that to your project?
When i upload my app to TestFlight it shows import built error and when i tried to make an ipa it shows error in exporting ipa. I tried so many times but same error comes. How to solve this issue.please help me. Below there is a screenshot regarding error comes during ipa creation process.
enter image description here
Solution Disable the "Bitcode" option. How to do it? Check out #stevechen answer New warnings in ios 9
What's the "Bitcode"? Bitcode is an intermediate representation of a compiled program. Apps you upload to iTunes Connect that contain bitcode will be compiled and linked on the store. Including bitcode will allow Apple to re-optimize your app binary in the future without the need to submit a new version of your app to the store.
Im using x-code 3.2.4 and I'm using the ios4.1 sdk.
I'm getting the following error when I try to call "ExtAudioFileOpenURL" from the audio toolbox.
Detected an attempt to call a symbol
in system libraries that is not
present on the iPhone:
_Unwind_Resume called from function _ZN15ID3ParserHandleC2EPvPFlS0_mmmPS0_PmE
in image AudioToolbox.
Why is this happening and how can I fix it?
Thanks,
db.
EDIT
In addition when running on a 4.1 device I get this error "error: 805297555"
What the hell?
The exact line of code causing the problem is this.
// Open an audio file and associate it with the extended audio file object.
OSStatus result= ExtAudioFileOpenURL (sourceURLArray[audioFile], &audioFileObject);
It's straight out of a sample code project. That sample code project runs fine.
I don't understand why if I start a new project with the same code I get errors.
This means that ExtAudioFileOpenURL is an unsupported API on the iPhone. ExtAudioFileOpenURL probably makes use of some exception handling API that is not available on the iPhone, which is why you are seing this sympton of the underlying error.
What I had to do in the end was completely uninstall the developer tools from my machine.
Then download the latest versions of xcode & ios SDK.
Everything works ok now.
Sadly I still don't exactly know what the problem was but at least things are running.