![]() But when I try to generate a Signed APK, I get a strange message after building telling me:ĪPK(s) generated successfully for module 'android-mobile-app-XXXX.app' with 0 build variants:Įven though the build seem to be successful I cannot find the generated APK anywhere (and considering the time it takes to give me that error, I don't even think it is building anything). Now I can compile my project and launch my app on my mobile, everything is working. I just updated my Android studio to the version 2021.1.1 Canary 12.Īfter struggling to make it work, I had to also upgrade my Gradle and Gradle plugin to 7.0.2. The permanent shutdown is not until March 15th.Īs in actions/checkout issue 14, you can add as a first step: Plus, this is still only the brownout period, so the protocol will only be disabled for a short period of time, allowing developers to discover the problem. Personally, I consider it less an "issue" and more "detecting unmaintained dependencies". The entire Internet has been moving away from unauthenticated, unencrypted protocols for a decade, it's not like this is a huge surprise. Second, check your package.json dependencies for any git:// URL, as in this example, fixed in this PR. ![]() This will help clients discover any lingering use of older keys or old URLs. ![]() This is the full brownout period where we’ll temporarily stop accepting the deprecated key and signature types, ciphers, and MACs, and the unencrypted Git protocol. See " Improving Git protocol security on GitHub". First, this error message is indeed expected on Jan. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |