I am working on a project which uses Apple's Network Extension Framework. However I cant make it work. I am following the Apple's tutorial SimpleTunnel. But I am getting this error when I try to save the profile
Save error: Error Domain=NEVPNErrorDomain Code=5 "permission denied" UserInfo={NSLocalizedDescription=permission denied}
In the documentation they ask for a special entitlements. I already sent an email for it but in the meantime I just want to finish the project without going live.
Is there any workarounds? Or should I just wait a couple of months to get the "special entitlements"?
Thanks.
Oh I should have checked apple dev forums before posting.
So the answer is I have to wait until I get the entitlements.
Due to the confused document and function missing of xcode 8.1, this cost me one whole week to find the solution.
Make sure you enrolled apple developer program (it's not free, you need to pay $100 per year)
Go to https://developer.apple.com/account/ios/identifier/bundle
Select Identifiers => App IDs
Click your app on the right(if there is no, you could create one with xcode),
Click edit button, check the network-extension checkbox
NOTE1: Since November 10th 2016, you dont need entitlement from apple to use network-extension
NOTE2: If you are using Hotspot Helper, go to https://developer.apple.com/contact/network-extension/
If you are using VPN Manager, simply use capability menu of xcode project config.
Related
In my TestFlight, I have more than 50 builds for Internal & external testers as well.
Today I uploaded a new build ver 2.5.1 from Xcode (My last ver on Apple store is 2.5). The build has been upload & I can see my build has been processed under 'Activity' tab but when I am trying to load 'TestFlight' tab, I am getting a blank screen as below, none of the builds are visible.
I have tried to open iTunesConnect on Safari, Chrome with the different type of user access (Admin, developer) but still getting the same screen.
Is this something wrong with Apple (I am trying from last 3 hours) side or I have to make any provision from my end.
Please suggest.
I've had the same issue and could only fix it by contacting Apple directly. I've requested a call through their "contact us" (on iTunes connect, not the main website) and got a call within a minute.
After explaining to the attendant my case (mentioning that there's a javascript error on the developer console!) she immediately sent a ticket to the iTunes Connect team and it was fixed one day later.
I had build problem regarding Testflight.Once I uploaded on testflight the build could not been appear for a day.So I had contact with apple guy.
https://developer.apple.com/contact/#!/topic/select
Raise your queries here, they will definitely resolve your problem.
Hope this link will help you.
Here is my answer,
I tried for the whole day but Testflight was not loading.
I did try after 10 hours in midnight and I found all my builds are visible & Testflight is loading.
I think there was some issue from Apple side & they did fix within a day.
I also found a link discussing the same issue
https://apple.stackexchange.com/questions/308244/testflight-tab-doesnt-load-in-itunes-connect
I've read a lot of tutorials and stackoverflow questions similar but I'm unable to figure out what's happening.
So I an an iPad application that I can successfully build in Xcode and on iTunes connect see the app version processing...
After a certain amount of time, it just disappears from the menu. As in it's no longer visible.
I've been following guides similar to: https://www.raywenderlich.com/133121/testflight-tutorial-ios-beta-testing
But the screenshots on internal testing show's a Select Version To Test option which I don't see:
Does anyone have any idea on how to debug this or what's going on? Because the Archive bundle looks like it's deploying it to the app store, I can see it on the iOS Builds activity but after processing I can't find it anywhere.
Recently we faced this issue couple of times. In iOS Builds section it shows Processing and after some time it disappears.
Reason is due to some errors/ issues with the ipa submitted to iTunesConnect.
Apple sends the error messages to people added in the Users and Roles section of iTunesConnect. You can check the people added in the the Users & Roles section and see the mails sent from Apple for any errors related to the app
Please add this key in info.plist
<key>ITSAppUsesNonExemptEncryption</key><false/>
Paste it before
</dict></plist>
This value means that the app uses no encryption, or only exempt encryption. If your app uses encryption and is not exempt, you must set this value to YES/true. Mine is not using encryption so I've set it to false.
It worked for me.
Apple is not going to any send any emails to any user regarding this issue.
Below you can see that testing for external testers are turned off:
same for internal testing:
but when I transfer app, one of the criterias are not met:
Why?
I had the exact same issue, resolved by removing all Tester and Build from the TestFlight as discussed above also (!important) remove everything fields at the App Information - Test Information.
For me it was localised test descriptions. Make sure you check that drop down list on the right and clear out info for all languages.
I just solved the transfer issue, you just need to expire your build from tester by following the steps below. and then app will available for transfer..
open your app and click on testflight then click on the icon of your app as shown in below screenshot.
The click on expire build.
Now you can transfer your app :)
I've search for a long time and to me this worked:
Clean all builds inside: My Apps --> App Name --> TestFlight
Go to: Itunes Connect --> Users and Roles --> Tab "TestFlight Beta Testers" and click in the name from another user that isn't you.
Save.
Go back to the App in Itunes Connect: "Itunes Connect --> App Name --> Transfer App" and attempt to transfer again by clicking in "Transfer App".
To me this works. Hope help someone.
i had the same issue i deleted (mark expired) all the versions of app testing version in App TestFlight section and done the trick for me ;) attach is the screen shot of activity.
Another possible reason:
When you delete all test information from TestFlight, make sure you delete it for every language.
In the testinformation page, select every localised language and check if the form is empty.
I struggled with this for an entire day, I tried everything and finally found another workaround:
1) Expire all the builds
2) Delete all testers
3) Clear all the informations in the Testflight tab
4) Delete all langages except the main one
And finally the step which fixed the Testflight criteria for us
5) Create a new app version (no need to submit or even edit it)
now you check transfer.
Good Luck.
I know it's an old question, but it still bugs people to this day.
So the solution here, after you have removed all the testers, and expired all builds, go to TestFlight > Test Information and clear all the fields.
Also make sure you delete any localization you might have there. Give it 5 minutes, after which transfering will be possible.
Not sure if this is going to help,
Check Users and Roles > TestFlight Beta Testers
Do you have a tester who is testing the app that you want to transfer?
I have the exact same issue and I'm currently getting from Apple "our engineering team is still working diligently to have this resolved for you". I have been supplied with a workaround:
Enable TestFlight by adding a tester to a build
Then deactivate the build, by turning off TestFlight beta testing
Attempt to transfer again
unfortunately, I still haven't been able to resolve the issue.
We found that in addition to the other answers here, logging out and logging back in to iTunesConnect allowed us to continue after it was saying TestFlight was still enabled.
I was facing the same issue, going inside tranferring app console multiple times automatically fixed the issue and started showing all criteria as met.
Do the same step as #Imran Iqbal answer, if your app is Sign-in Required, uncheck Sign-in Required also, like:
then, you can transfer app.
I've exactly the same problem and could not solve it. The good news: After contacting Apple, they have confirmed a bug and they're working on a solutions. Apple confirmed also, that many developers ran into this.
Got that workaround from the support (that did not work for me):
1. Enable TestFlight by adding a tester to a build
2. Then deactivate the build, by turning off TestFlight beta testing
3. Attempt to transfer again
It looks like this is being done on purpose for new apps.
Now, A newly created app CANNOT be transferred into an account, until 14 - 21 days have passed.
An expiration period.
First, You must remove all build and user from TestFlight of that app. After its looks like below.
If you still not match last criteria than Sign Out and login again.
Creating new app version did it for me! Thanks!
The tricky solution is to enable testing again, add some tester in. The visit the TestFlight and under test flight users, you will see old active test flight users. Simple delete them.
When I try to achrvie the Xcode showing the message " Fetching list of teams from the Developer portal " . It always timed out. Can't fetch the team.
I Accounts it Showing Apple Id not having any Development Teams. I have added the Apple Id
I have just tried to make same and it's working properly for me. So, problem is not from Apple Side.
Please check your internet connection properly and try again.
Apple is facing some big problems for last two weeks and due to iTunesConnect Outage they are facing some problem in uploading the new application on AppStore. But here you can also check if your internet connection is good and make sure it is not low internet connectivity.
Here there is also some issue with Xcode 6.2 so better you delete the team and add them again and try to upload the application via Xcode.
In case you are still facing the same issue then better export the .ipa file and upload with "Application Loader" software from Apple.
It's because of low internet connectivity. If your internet connection is not proper then you cannot get an apple account through which you can make an IPA.
July 2015
I'm using XCode 6.4, and today, its been happily building Ad-Hoc .ipas for me all day, but now, on the same MacBook Pro, it's timing out every time on this same "Fetching list of teams from the developer portal" message.
Sometimes, it (eventually) returns a "The request timed out" message, sometimes I just get this...
And no, this isn't an internet problem...
This issue has been reported on several StackOverflow threads over the past few months. Usually it works, but sometimes it doesn't, and, in usual Xcode fashion, it gives no hint as to the cause/solution.
(How can the same company produce such a fantastic OS and hardware, yet their development environment is so consistantly bad, year after year...?)
Update
Sigh.
Out of desperation, I rebooted my MacBook, and now, it happily manages to load the list of teams.
(Just closing all Xcode instances wasn't enough to fix the issue.)
Welcome to the 1990s, folks.
I've tried everything that been said. Nothing works, what I do is try and cancel every moment that you know it will fail. Like a traffic that cant continue because of load of request.
I'm trying to upload an app with Application Loader but I get following error :
Apple's web service operation was not successful Unable to
authenticate the package: 54005906.itmsp An unknown error occurred.
(2010)
What is the problem? I really can't find any info.
Its was problem with Apples process. Worked the day after!
I would check following
1. Profile, username, password, certificate 2. Clean Build and Try again.
I kept getting it for several days until I changed Deployment Target from 3.1.3 to 4.3.
I just selected Standard Architectures in both Project and Target, and it worked for me.
I had the same error but fixed it by changing Build Active Architecture Only from
Release YES
to
Release NO.
When submitting a question like this you need to include all the error messages
If you choose to post only the error messages that you think are relevant, you are probably going to choose the wrong messages. If you know how to indentify the extraneous info, you probably don't need to post a question to StackOverflow at all. ;-)
When submitting a question like this there are a few things to note:
• If you submit enough failures in some given time frame, Apple will stop allowing you to connect/submit for some other time frame!
- This is a situation that seems to correct itself overnight in most cases. You can use a different authorized account to get around this. (Create a new one if you gotta.)
• The first 2 items are red herrings
Apple's web service operation was not successful
In spite of how it sounds, this doesn't mean it couldn't connect. This simply means that the ultimate goal was not successful.
As a metaphor: if (ApplicationLoader.DeliverYourApp(SelectedFile)){log("Delivery Successful");} else {msg("Apple's web service operation was not successful");}
Unable to authenticate the package: 81680085.itmsp
Before Apple accepts your package on their server, they want it to pass a few "field sobriety" checks.
From their perspective, it's like "cloud computing". They are saving server resources by doing analysis in the cloud. And the cloud is the workstations of all their developer.apple.com members.
• The "Background Activity" panel (revealed by clicking "Activity...") is very useful to watch.
Seeing "Could not start delivery: all transports failed diagnostics" makes you think there is some form of connection or login error (especially when combined with the top 2 errors. If you open the Background Activity panel early on and watch the entire process, you see that the message that is RED in the screenshot above actually goes through these states:
Upload package to the iTunes Store
Authenticating with the iTunes Store
Verifying assets with the iTunes Store
Could not start delivery: all transports failed diagnostics
Finally, the error in my screenshot actually means...
The IPA file I was given fixes the bug that prevented my previous upload from succeeding, however, the developer forgot to increment the build number and Apple re-rejects it out of principle. This could be avoided if they would implement a build script that does something alone the lines of git log --oneline | wc -l. This is pretty much exactly the way I do it in my projects.