Because when the developer is troubled, the IDE will collapse. Then I realized there is no point in scrambling and letting the Android studio know I’m scared. Such as, clean the project, restart the IDE, rebuild it, etc. I tried many other known troubleshoot methods. It should because it is the equivalent of a task manager in windows. So what happened?Īs every other Android developer does, I tried the mighty ‘Invalidate Cache/Restart.’ Hoping that this will solve the issue. And I was pretty sure I didn’t make any code changes. It was running without any errors all the while. Invalid main APK outputs : EarlySyncBuildOutput(type=c 1fdc3a85, apkType=MAIN, filtersData=, version=0, output=D:sample projects\sample_app\app\build\outputs\apk\debug\app-debug.apk),EarlySyncBuildOutput(type=c 1fdc3a85, apkType=MAIN, filtersData=, version=0, output=D:\sample projects\sample_app\app\build\outputs\apk\debug\output-metadata.json) I was sipping my coffee, watching the Gradle building my app, and all of a sudden, an error popped up in the build window. Or maybe Android studio is still learning. Sometimes I feel like the world of Android development is funny.
How to fix the error invalid main APK outputs in Android
0 kommentar(er)
