today I was editing and apk (A modified kik client) on the apktool known as "advanced apktool." I edited a couple different apk apps to test after I received my problem, to see if it was just the apk. It wasn't. After I decompiled and edited the app, I recompiled, signed the package, and dragged the finished product to my dropbox. I went to download it on my android when I got the error"application not installed". My friend could not install either as he got a "error parsing package" error. I then tried zip aligning and downloading, still no luck. I don't know why I cannot download it. I have no other interfering package names. I tried it with and without the original app. It did not work. I believe it the way I saved, or maybe the signing key. It is not my phone, as my friend could also not download it. Thank you for reading, please ask if you need clarification.
Related
I'm trying to publish my first app to the Apple App Store. It's an Expo React Native App.
I'm currently submitting the build to the app store with eas submit -p ios --latest. However, I'm getting the error:
Failed to create App Store Connect API Key.
UnexpectedAppleResponse: The specified resource does not exist - There is no resource of type 'apiKeys' with id 'XXXXXXXXXX'
I'm watching an online tutorial and I've been able to follow every step until now. Any advice on how to fix this error would be greatly appreciated. Thank you in advance!
You need update your EAS to 0.60.0
npm install -g eas-cli
I had the same problem.
Work for me, friend
We fixed this issue by next steps
1: Upgrade your eas-cli running: npm install -g eas-cli
2: If you're publishing by first time your app, you need request access in to your App Store Connet, by this link,
https://appstoreconnect.apple.com/access/api
Select Users and Access, and then select the API Keys tab.
Then, click in "Request access" blue button, and then, your api keys generated will appear there.
Then download any key, open whit text editor and paste the path of file in eas terminal, by selecting "[Enter an App Specific Password]"
Important: Is not necessary creare a new key if you has already downloaded your key
We hope this works for you.
And that's it.
There is a bug in Apple's infrastructure that does not propagate newly created objects for a long time (up to 14 seconds in my experiments). Apple responds saying the resource does not exist when the cli tries to download the key and it hasn't fully propagated. I just released a fix in eas-cli to retry in this scenario, it should be available in v1.1.1.
I have been trying to upload an iOS app to Appstore but its only appearing on "Activity" tab for 3-5 minutes and then disappears.
Then I got an email from Apple saying that my app is rejected because it is using UIWebView in one of the view controller. I deleted that particular screen and reuploaded the app and had the same error email.
Then I checked my third-party sdks like FacebookLoginSDK and GoogleSignInSDK and updated those and then checked that if the app has no UIWebView which it did not. Then i reuploaded the app but this time again I had the same error email. I have searched the whole storyboard source code and the whole app code to look that if there is any sign for UIWebView but there is nothing, but still I am getting this email.
I also tried deleting 'Derived Data' folder several times and cleaning the build folder also but nothing helps.
On the other hand I have uploaded a different app today which had UIWebView and it got approved but I also got the same email for not using UIWebView.
Does anybody had this kind of experience or can anybody tell me whats going on ?
I got the same issue before.
If you have uploaded the build and showing it in activity tab for few minutes then its not mean that issue is only about UIWebview but there can be some other issue as well.
I have uploaded my app n got the mail related to UIWebview, so I coverted the UIWebview to WKWebView and again I uploaded but that time same thing happend.
I failed to tackle the problem.
Then I mailed to Apple Developer Support and they replied like
Any of the third party library internally using some privacy data you should ask permission for the same.
Then I checked Info.plist, I have given each permission in list still how it comes that we don't understand.
Finally then after whole search the one third party library internally using motion related data without permission so this happened.
Then I have added that in plist and then again uploaded and its approved.
So please you can check your info.plist and also check whether your third party library using any privacy sensitive data without permission or not.
May it help you at some point.
Make sure you update all your plugins to the latest version!
Check this: https://ionicframework.com/blog/understanding-itms-90809-uiwebview-api-deprecation where you can find the plugins that have known issues concerning the old WebView usage.
But be aware that uninstalling and re-installing some plugins will NOT will not install the latest available version of the plugin!
So to be sure that you are re-installing the latest version of a plugin, go to the github repository of the cordova plugin and search for the plugin.xml file and open it. Then, copy the version string found in the root xml element.
Finally, install the plugin like that: ionic cordova plugin add plugin_name#copied_version
<?xml version='1.0' encoding='utf-8'?>
<plugin id="cordova-plugin-firebase" version="2.0.5"
xmlns="http://apache.org/cordova/ns/plugins/1.0"
xmlns:android="http://schemas.android.com/apk/res/android">
<name>Google Firebase Plugin</name>
...
...
...
</plugin>
Are you using the AdMob plugin?
It is not enough to check for the absence of "UIWebView" strings!
You have to make sure that all third party plugins are up to date.
One of the trickiest situations I had went to is when I had tried to update an app (using AdMob) on the AppStore after Apple started rejecting apps using the UIWebView.
The generated iOS source code has no UIWebView references, but still rejected!
After a long headache, I realized that the Google AdMob SDK version I'm using is out of date, knowing that I had updated the AdMob plugin from the CLI, but it seems that the SDK is not updated when updating from the npm.
Finally, I had downloaded the latest AdMob SDK from this link https://developers.google.com/admob/ios/download and replaced it in the source code of the AdMob SDK plugin. Then I had followed the instructions found in this link https://developers.google.com/admob/ios/quick-start to update the code in the xCode.
Like I said in the title, I keep getting the error "This Action Could Not Be Completed. Try Again. (-22421)" when trying to upload my app to iTunes connect. I did it a few weeks ago and it worked fine. Since then I only made a few small text changes, nothing major, and not it won't work.
I looked around and people were saying it could be an issue with Apples servers but its been 4 days now since I've been trying.
I've also noticed when I archive my app I get the error "section "__const_coal" is deprecated" in Xcode 8.2.1. This doesn't show up when I build or run on my phone, but only when I archive. I tried this on stack overflow and tried it but it didn't work and other than that I've found no solutions.
I really need to push this update but I'm completely lost on what to try next.
If anyone can help me fix this I will be forever grateful!
I had the same issue a couple of days ago.
You need to manually update the iTMSTransporter.
To do it just open a terminal and run the following code:
cd ~
mv .itmstransporter/ .old_itmstransporter/
"/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/itms/bin/iTMSTransporter"
It should show something like:
<main> INFO: Transporter is searching for updated software components.
It took about 10 minutes to finish in my case, but I was on a really slow connection.
Tell me if it worked for you too!
You can try following solutions:
Use Application Loader to upload your app, as Xcode organizer can't upload file (rejects IPA) sometimes, without genuine reason and it's frequently occurring issue, with Xcode Organizer, that apple could not resolve permanently.
Solution for error code: 22421
Apple app upload server is not working properly (not in
connection or lost connection during file upload). Just wait and try
again later (may be after a day).
Fluctuation in your network
connection, during file upload.
You may not have added privacy
statements in your info.plist file.
Cocoa Keys: Here, is list of keys (with privacy statements) that you should consider to add in your info.plist file, if you have used that service in your application.
Nowadays, you may also face, this error code: 90186 (with app loader)
Outdated application loader can be reason of this error. Use latest Xcode tool and use application loader from Xcode Tool.
Incorrect/invalid provisioning profile, associated with your build. Ensure, your have used correct provisioning profile (A provisioning
profile with Distribution/Production mode is require. A Development mode provisioning profile won't allow your to upload app on store.)
You can find latest Application Loader Tool from latest Xcode Tool: Xcode -> Open Developer Tool -> Application Loader
I have a very mysterious problem.
I am somehow not uploading my new app versions correctly even if everything it seemingly correct. I determine this by download the "new" versions and seeing nothing has changed.
1)
Before release I test my changes are included and working on device-debug + device-adhoc.
2)
I then build and deploy for app store. Before uploading my .ipa file into "Application Loader" I make sure the .ipa file has just been generated. I then select it and the upload/verification process goes find without errros and some days later I get a message new app has been released...
3)
I then uninstall my existing app (just to make sure) and download and install the new app version from appstore - it is still the same. This is driving me nuts. I think I have tried to eliminate potential places where I could have errored, but somehow somewhere something is going terrible wrong for me. This is a fairly recent new problem - never had it in the past.
I am hoping if somehow can think of ways I can diagnose at what steps this is going wrong... I know it must be me that have an error somewhere. I recognize when something looks like a "Doh!" thing, but I believe I have tried a varity of methods to pinpoint it.
I have also tried clear out out scratch/temp directory before building + deploying. However, I am still wondering. Could it be some cache/path setting somewhere that makes Delphi compile incorrect app executable only when doing release builds? (I have of course also long time ago deleted all old directory paths that could contain earlier builds, but still...)
I did not see that you have already tried it on a new buddy phone & it worked. So editing my answer.
Can you try to remove your device ID from the profile settings in developer page & give a try downloading it.
There may be problem in building & compiling with Delphi.
Here is a post that differentiates between the same.
Please do see the accepted answer for that question here.
Hope that helps. (I know you are really pissed off waiting for the whole long app approval process & annoyed seeing the same old version.)
I had a buddy try download the latest app version, and he successfully and ran the new version... So I now must assume it is somehow my iPhone that is strange. I remove all app instances (debug, old appstore download) - then download the new version from app store. After that, my iPhone shows the "new" text on the launch icon, but still launches an old version... somehow
Just created an .apk with the Publish Android Application option, created a keystore with key and uploaded to the Google Play app store. Everything worked, but when I tried to download the app from the app store i got an error message resembling "The application has an incorrect signature". I thought the "Publish Android Application" part of Xamarin.Studio was supposed to fix everything?
I ran the following command on the .apk afterwards: jarsigner -verify -verbose -certs app.apk At the bottom it said the following: This jar contains entries whose certificate chain is not validated.
Please help, would love to have the app out today :)
My problem was simple. XamarinStudio was setup to use Java1.7, setting it to use Java1.6 fixed it :)