Your app is using a version of MoPub containing a security vulnerability. Please see this Google Help Center article for details, including the deadline for fixing the vulnerability.
Resubmit your application with MoPub SDK v4.4.0 or higher.
See https://support.google.com/faqs/answer/6345928?hl=en for more details.
Download the latest version of MoPub here: https://github.com/mopub/mopub-android-sdk
Related
I did run bundle exec fastlane match_development create:true as usual.
My fastlane suddenly stopped working reporting apple developer website is under maintenance.
and take look the error information.
Please update using bundle update fastlane
/Users/knight.lu/.rvm/gems/ruby-2.3.0/gems/spaceship-0.38.1/lib/spaceship/client.rb:414:in `parse_response': [!] (Spaceship::Client::UnexpectedResponse)
Any idea about The Apple Developer website is undergoing maintenance. For details, visit developer.apple.com/system-status.
Seems like they are changing api endpoints, but getting mixed issues from people. Follow the current issue on fastlane here.
The fix will probably require a fastlane update.
There is no solution for now. Looks like Apple changes API somehow. But you can use match in readonly mode and update PPs manually: https://github.com/fastlane/fastlane/issues/8208
You can check all services here
Apple Developer System Status
I am trying to publish app to google play appstrore and rejected. It seems that Google made some security update, because previous version of apps were published? Is there any solution for this?
Note: i have updated latest SDK from manager
Your APK has been rejected for containing security vulnerabilities, which violates the Malicious Behavior policy. If you submitted an update, the previous version of your app is still live on Google Play.
To properly handle SSL certificate validation, change your code in the checkServerTrusted method of your custom X509TrustManager interface to raise either CertificateException or IllegalArgumentException whenever the certificate presented by the server does not meet your expectations. To confirm you’ve updated correctly, submit the updated version to the Developer Console and check back after five hours. If the app hasn’t been correctly upgraded, we will display a warning
Problem is using OpenSSL 1.0.1l in the official 4.5 release SMF and next releasing an upgrade to the 4.5 players to OpenSSL 1.0.2g which is the latest release. Wait SMF 4.5.3.
I wouldnt hold my breath waiting for app studio 4.5.3. I have been in touch with them and they said that they have dropped the desktop IDE as their cloud IDE is doing much better. They gave also mentioned that in 6 months time their cloud IDE will have a WYSIWYG editor.
Hopefully the trusted manager error will not occur when publishing with the cloud IDE
I try updating Phonegap application to 2.9 with updating facebook sdk to recent version.
I've completed update guide and re-attached Facebook SDK. Could find an answer that would help in other stackoverflow issues.
I'm getting error
ld: 41 duplicate symbols for architecture i386
What I have tried so far:
Removed Facebook SDK from Buid Phases: this leads to facebook classes not found. Reverted.
Verified plugin is in 'ios' subgroup
Verified frameworks are attached
Config screenshots: 1 2 3
What am I missing?
Which version of Facebook iOS sdk are you using? If it is 3.5, try downgrading to 3.2 and see if that works. Phonegap Facebook plugin is a bit outdated and seems to have issues with the latest ios sdk.
I have created an app for iPhone in phonegap.
In starting I used phonegap 1.5 and submitted this app to app store.
But now I upgrade my app and try to submit to app store.
Now it is showing error related to Unique Identifier.
To resolve it I have to upgrade phonegap from 1.5 to 2.7.
I checked link
But here upgrade guides are available particular version to version.
Go one by one through the upgrade guides until you get to the version that you want.
I had same problem but, with android.
My colleague checked all the stages provided here.
She reviewed all steps and found that there are minor differences in stages.
So here is how we upgraded from 1.5 to 2.6 for android.
I suggest you to review the stages for iOS and find out minor differences.
Instead of going stage by stage, check if there are common steps and follow them directly from 1.5 to 2.7
I downloaded a pre-release version of the iPhone SDK and tried to update one of my existing apps using a binary I built with it. Obviously you are not supposed to do this but I had forgotten about the warning when I installed the pre-release SDK. Anyway - I have two questions:
Can I simply set the base SDK to an earlier version in the build settings and get around this problem?
If not, then what should I do?
You need to download the release version of Xcode with the release iPhone SDK. You can't use the SDK downloaded from the iPad beta version for any release products.
Just go to http://developer.apple.com/iphone/index.action and click on iPhone SDK 3.1 and download it. Then build your app bundle with that and submit it to Apple.
Before you download a pre-release version of the SDK from developer.apple.com, there are several prominent warnings, one of which clearly states that pre-release versions of Xcode / iPhone SDK can NOT be used to build production binaries. So the answer to 1. is an emphatic no.
As far as I can tell, the only option to be able to build production binaries that iTunes Connect will accept is to delete the pre-release version of Xcode / iPhone SDK and re-install the older stable version.
If you upgraded using the beta download (as opposed to installing on a fresh box that has never seen SDK or Xcode), set the base SDK to a released version of the OS. Compile a Distribution build, submit to the app store. The old SDK is still there, so that will get used. All of the prominent warnings I have seen state the the SDK cannot be used, without mention of Xcode.
Before anyone scoffs, note that I submitted an app on March 13 using the version of Xcode (3.2.2) included in Beta 4, setting Base SDK to 3.1. It was approved on the 15th. I've also done this during the 3.0 beta for 2.x apps.
EDIT: on the other hand, acceptance apparently isn't always guaranteed (note that this person had also submitted an app that did get accepted): The binary you uploaded was invalid. A pre-release beta version of the SDK was used to build the application