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
Related
I am running into an issue with universal links and not sure what's going on. I am not using Branch or any third party.
Once i restart the phone, it works. After that for some reason, it stopped working, and I have to restart the phone again.
Not only my phone but also happening on the other phones.
Have any one run into that issue?
Best,
This is a known issue with iOS 11.2. You can refer to this post mentioned in the comments. This is not an issue with the third-party, it is an issue with iOS 11.2 not downloading the AASA file consistently. Branch and other third party services still leverage this AASA file downloading to run their deep linking. I have yet to run into this issue in iOS 11.3, but the radar is still open.
Recently I've been sent sources of the app I need to build and deploy to TestFlight. Unfortunatly whenever I try to run the app on my test device in debug mode or the one installed from TestFlight, it fails to start throwing the following error message:
dyld: Library not loaded: #rpath/Alamofire.framework/Alamofire
Referenced from: /var/containers/Bundle/Application/77FB1F81-25F5-4670-ACF1-F814543B9A0E/MyApp.app/MyApp
Reason: no suitable image found. Did find:
/private/var/containers/Bundle/Application/77FB1F81-25F5-4670-ACF1-F814543B9A0E/MyApp.app/Frameworks/Alamofire.framework/Alamofire: code signing blocked mmap() of '/private/var/containers/Bundle/Application/77FB1F81-25F5-4670-ACF1-F814543B9A0E/MyApp.app/Frameworks/Alamofire.framework/Alamofire'
/private/var/containers/Bundle/Application/77FB1F81-25F5-4670-ACF1-F814543B9A0E/MyApp.app/Frameworks/Alamofire.framework/Alamofire: code signing blocked mmap() of '/private/var/containers/Bundle/Application/77FB1F81-25F5-4670-ACF1-F814543B9A0E/MyApp.app/Frameworks/Alamofire.framework/Alamofire'
/private/var/containers/Bundle/Application/77FB1F81-25F5-4670-ACF1-F814543B9A0E/MyApp.app/Frameworks/Alamofire.framework/Alamofire: code signing blocked mmap() of '/private/var/containers/Bundle/Application/77FB1F81-25F5-4670-ACF1-F814543B9A0E/MyApp.app/Frameworks/Alamofire.framework/Alamofire'
The app uses COCOAPODS as a dependency manager. In the Podfile there's TRON pod which depends on Alamofire framework we have problem with.
The app built, signed and validated successfully during submission and debug builds. So it doesn't seem to be related to certificates or provision profiles. But I've anyway recreated certificates and provision profiles. (although I believe this is not the case as the app is submitted to app store successfully). Developer of the app builds and runs the app with no problem. We checked the versions of used tools and libraries and they seem to be indentical. (xcode version, cocoapods version, pods dependencies).
I even tried to build the sources with all dependencies installed (pod install), that he builds.
There're similar questions on SO, but they don't seem to deal with COCOAPODS when they face this problem. The solution is usually involves manually Embedding frameworks. But this is not the approriate solution for us, as all demendencies integrated through COCOAPOD scripts.
What else can cause the problem?
This is an issue with iOS 13.3.1. All dynamic frameworks being compiled to the newest release of iOS 13.3.1 are experiencing this issue when running on a personal provisioning profile/developer account.
You can:
Use a non-Personal Team provisioning profile (paid developer account).
Run on the 13.3.1 simulator.
Test on a real iOS device running 13.3 or lower.
This issue will be fixed in 13.4 Beta version though.
The problem was not related to specific app. Building any app even the most simple one produced the same error.
Solved by reinstalling Apple Worldwide Developer Relations Certification Authority, even though it wasn't expired.
Steps:
Open Keychain Access
Remove the certificate from Login and System Keychains
Download certificate from https://developer.apple.com/certificationauthority/AppleWWDRCA.cer and install it to both keychains. (double click it)
JIC: Remove provision profiles, clean project, restart xcode/Mac :-)
in my case, the problem was related to Apple Worldwide Developer Relations Certification Authority and i solve it by change trust from always to use system defaults.
open keychain access
right click on Apple Worldwide Developer Relations Certification Authority and select Get Info
Expand trust
change when using this certificate to use system defaults
Remove or comment # use_frameworks from pod file and clean build folder. Its worked on my end.
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 understand Swift is a new language and I also understand what Beta means but still it is possible and necessary to test deploy newly creates apps on the phone without updating it to iOS8.
However when I tried to use the TestFlight service, as I have done in the past (I know Apple has acquired the company), all works great until TestFlight tries to install the app on the phone. At that time one receives an error message ..."cannot be installed at this time" ...
Does anybody have an idea how I can make TestFlight work or have a viable alternative so I can test my app on the phone of somebody remote.
Any insight is highly appreciated.
Export the IPA as you normally would, making sure that you use your AdHoc provisioning profile for the release (in the build settings).
Then here's the workaround to get it to work with testflight.
Open a terminal and go to the directory where the IPA lives
ditto -xk myapp.ipa /tmp/myapp
ditto -ck --norsrc /tmp/myapp ./myapp-after.ipa
rm -rf /tmp/myapp
Upload myapp-after.ipa as your TestFlight build.
Anyone getting the following issues on a recent build that you trying to upload to the store?
1. Your app contains non-public API usage. Please review the errors, correct them, and resubmit your application.
2. Apps are not permitted to access the UDID and must not use the uniqueIdentifier method of UIDevice. Please update your apps and servers to associate users with the Vendor or Advertising identifiers introduced in iOS 6.
It is thus failing validation and not uploading.
Apple recently disallowed developers from accessing the device's UDID (Unique Device Identifier), but some third party libraries haven't updated yet. In particular, some people have been having problems with Google Analytics. Another post on here recently gave a pretty good answer: App rejected, but I don't use UDID
The library that seems to be the most common one causing this is Google Analytics' debug library (libGoogleAnalytics_debug.a) - make sure you're not linking against the debug version in your production build, but instead link against the release version (libGoogleAnalytics.a)
The other one I encountered was PayPal's Mobile Express Checkout Library (MECL). For this one there's no fix since they don't seem to be planning on updating the MECL to not use the device token. You'll have to switch to PayPal's MPL library or their new SDK which is US-only.
To find the offending library/framework, run this in your project folder:
find . | grep -v .svn | grep "\.a" | grep -v "\.app" | xargs grep uniqueIdentifier
It will have some trouble traversing some folders so see the output and manually go into the folders that it can't get to, and run it again in there. The command above came from this SO answer