Jump to content

[TOPIC: topicViewTemplate]
[GLOBAL: userSmallPhoto]
Photo

Build failed
Started by richard11 Feb 27 2020 07:07 AM

7 replies to this topic
[TOPIC CONTROLS]
[/TOPIC CONTROLS]
[modOptionsDropdown]
[/modOptionsDropdown]
[reputationFilter]
[TOPIC: post.html]
#1

richard11

[GLOBAL: userInfoPane.html]
richard11
  • Contributor

  • 552 posts
  • Corona SDK

It's been a while now since I compiled an Android build and I've just updated to the daily build 2020.3575 so unsure whether this is specific to this version or if it would have happened had I not updated first, but either way it seems I can't currently build...

 

 

15:01:20.483  Using custom build id from app bundle: 00000 (AppSettings.lua)

15:01:20.483  
15:01:20.483  Using custom Build Id 00000
15:01:20.608  Excluding specified files from build: 
15:01:20.608     excluding: LaunchScreen.storyboardc
15:01:20.608     excluding: Icon.png
15:01:20.608     excluding: Icon-*dpi.png
15:01:20.608     excluding: Images.xcassets
15:02:06.869  @ver > NUL
15:02:06.869  Picked up JAVA_TOOL_OPTIONS: -Duser.language=en
15:02:06.869  Exception in thread "DisconnectableInputStream source reader" org.gradle.api.UncheckedIOException: java.io.IOException: Access is denied
15:02:06.869  at org.gradle.internal.UncheckedException.throwAsUncheckedException(UncheckedException.java:61)
15:02:06.869  at org.gradle.internal.UncheckedException.throwAsUncheckedException(UncheckedException.java:41)
15:02:06.869  at org.gradle.util.DisconnectableInputStream$1.run(DisconnectableInputStream.java:125)
15:02:06.869  at java.base/java.lang.Thread.run(Thread.java:844)
15:02:06.869  Caused by: java.io.IOException: Access is denied
15:02:06.869  at java.base/java.io.FileInputStream.readBytes(Native Method)
15:02:06.869  at java.base/java.io.FileInputStream.read(FileInputStream.java:256)
15:02:06.869  at java.base/java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
15:02:06.869  at java.base/java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
15:02:06.869  at java.base/java.io.BufferedInputStream.read(BufferedInputStream.java:345)
15:02:06.869  at org.gradle.util.DisconnectableInputStream$1.run(DisconnectableInputStream.java:96)
15:02:06.869  ... 1 more
15:02:06.869  
15:02:06.869  FAILURE: Build failed with an exception.
15:02:06.869  
15:02:06.869  * What went wrong:
15:02:06.869  Execution failed for task ':App:packageReleaseBundle'.
15:02:06.869  > A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
15:02:06.869     > File 'root/res/drawable-xxhdpi-v4/ic_maps_indicator_current_position_anim1.png' uses reserved file or directory name 'res'.
15:02:06.869  
15:02:06.869  * Try:
15:02:06.869  Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
15:02:06.869  
15:02:06.869  * Get more help at https://help.gradle.org
15:02:06.869  
15:02:06.869  BUILD FAILED in 43s
15:02:07.618  Android build failed (1) after 47 seconds

 

Any thoughts please?



[TOPIC: post.html]
#2

fjefferson

[GLOBAL: userInfoPane.html]
fjefferson
  • Observer

  • 2 posts
  • Corona SDK

I had the same problem.
Not working on versions 218.3326 and 2020.3575


[TOPIC: post.html]
#3

richard11

[GLOBAL: userInfoPane.html]
richard11
  • Contributor

  • 552 posts
  • Corona SDK

Actually I've just spotted https://forums.coronalabs.com/topic/76892-error-while-building-for-android-error-code-256/ and it sounds like this could be another instance.

 

The only plugin this app uses is our own Android Cusom Camera plugin which is a native one, so ref Vlad's final comment within that thread, it sounds like we need to update this plugin to use the latest native plugin template and push this out before apps that use it will compile in the latest daily builds?

 

If this is the case then presumably all native plugins that were built before the latest template, which seems to be dated 15th Feb, will be causing build fails at the moment? I.e. plugins built in native code before February 15th are now breaking the Corona build process?



[TOPIC: post.html]
#4

stalxerhd

[GLOBAL: userInfoPane.html]
stalxerhd
  • Enthusiast

  • 44 posts
  • Corona SDK

Build server is not available again, it goes offline periodically, so 1-2-3 builds could be successful and 4 not, or 1 be successful and others are not. Just spotted this problem, wach status.coronalabs.com - a whole week again!



[TOPIC: post.html]
#5

richard11

[GLOBAL: userInfoPane.html]
richard11
  • Contributor

  • 552 posts
  • Corona SDK

Does 2020.3575 still use the build servers? From the console output I assumed this was all local, but I could be wrong...

[TOPIC: post.html]
#6

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 26,680 posts
  • Enterprise

iOS still uses build servers. Android does not, however all build still call back home to verify authorizations and plugin licenses.

 

Rob



[TOPIC: post.html]
#7

richard11

[GLOBAL: userInfoPane.html]
richard11
  • Contributor

  • 552 posts
  • Corona SDK

Finally had chance to dig into this again.

 

If I remove our camera plugin from the build.settings, the build process completes successfully so this definitely was another instance of the issue discussed at https://forums.coronalabs.com/topic/76892-error-while-building-for-android-error-code-256/

 

I've now therefore followed the same instructions I wrote here following the advice @vlads gave, to move this plugin into a fresh copy of the native template shipped with Corona: https://forums.coronalabs.com/topic/76798-android-studio-35-andor-64bit-builds-failing/

 

Then followed the last few paragraphs of the old tutorial I wrote at https://www.qweb.co.uk/blog/creating-a-corona-native-plugin-with-android-studio to repackage this up as a plugin (note my comment from 14/12/2019 too, correcting some of the instructions due to changes to the Gradle build process).

 

Presuambly the new .jar file will fix the build issue, so I've pushed this out to the Mercurial repository and am now waiting for the simulator to pick up an update.

 

Will this actually synchronise and work, or are the build servers no longer accepting updates? I'm aware the marketplace itself isn't accepting new submissions but I'm not sure what the status is for updates to the bucket repositories...



[TOPIC: post.html]
#8

richard11

[GLOBAL: userInfoPane.html]
richard11
  • Contributor

  • 552 posts
  • Corona SDK

To answer my own question - yep, the sync worked and the build process does indeed now complete. I managed to screw up a permissions requirement and have had to push another update out, but once this too has synchronised, builds should work again for anybody else using our camera plugin.

 

Sorry that it's turned out to be our plugin that's caused this one. It would be nice if the build process didn't spontaneously stop understanding native plugins built using older templates and effectively break without warning! ;-).




[topic_controls]
[/topic_controls]