New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Always get Transportation Failed
for App Extension Target
#5467
Comments
Transportation Failed
for Extension TargetTransportation Failed
for App Extension Target
Hi @macbaszii Are you able to upload the same ipa to iTunes in other ways without issues? What happens if you pass the ipa directly as a parameter? Thanks! |
@TKBurner Sometimes I get the same result, but I can eventually release the app manually via Application Loader. But with Fastlane, both CLI and CircleCI. I always get the error. |
@macbaszii Can you let me know more about your frameworks file? It seems like that is why your project is getting rejected. Thanks! |
I'm seeing this issue as well. Trying to submit an iOS 10 Message Extension for TestFlight |
Adding this run script to the end of my extension appears to remove this error. |
Closing this as a non-fastlane issue. |
Issue Description
I always get this error while the app is successfully built and being sent to iTunes Connect.
It's about
App Extension Target
(I have a Sharing Extension in my app)I tried everything that I've found via Google such as
Run this script in Extension Target
or Change
Embedded Content Contains Swift Code
flag in Extension Target's build settings toNO
These solutions don't work for me.
I run the fastlane command both on my Macbook Air and on CircleCI, all failed.
if you want some more informations, please tell me.
Thanks in advance.
Complete output when running fastlane, including the stack trace and command used
Configuration Files
Fastfile:
Environment
fastlane version (run
fastlane -v
):1.98
Do you use bundler to execute fastlane (i.e.
bundle exec fastlane
)?NO
Do you use a Ruby environment manager (e.g.
chruby
,rbenv
,rvm
)?NO
The text was updated successfully, but these errors were encountered: