Jump to content

[TOPIC: topicViewTemplate]
[GLOBAL: userSmallPhoto]
Photo

Corona builds doesn't work
Started by aclementerodrguez Sep 14 2019 10:42 PM

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

aclementerodrguez

[GLOBAL: userInfoPane.html]
aclementerodrguez
  • Enthusiast

  • 46 posts
  • Corona SDK

Hi there,

 

I'm using Corona 2019.3480 due to is the last build before the 64-bits support and the recent builds does'nt work for me ( No one has been able to tell me so far why ).

 

This is the Warning when I trying to make the build: (see the attach image)

 

PD: my internet is Ok



[TOPIC: post.html]
#2

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 26,625 posts
  • Enterprise

2019.3490 is the last 32-bit version.

 

Your image did not attach. Can you re-submit?



[TOPIC: post.html]
#3

stalxerhd

[GLOBAL: userInfoPane.html]
stalxerhd
  • Enthusiast

  • 43 posts
  • Corona SDK

I installed the latest build (Corona-2019.3530) and my builds don't work to on test devices and BlueStacks. It shows a black screen after initial "Build by Corona", or crashes to the main screen with no response after the start. Move back to Corona-2018.3326 and everything goes ok.



[TOPIC: post.html]
#4

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 26,625 posts
  • Enterprise

@stalxerhd, we can't magically troubleshoot anything based on this. You need to plug a test device that's crashing in and show us the results on an "adb logcat" when you run the app and see what's crashing. Please use pastebin.com or something similar to share this console log dump.

 

Secondly, I know we ask this a lot, but we really need to see your entire build.settings. Putting it in pastebin.com or similar and sharing a link is preferable to a long code post, but if your build.settings isn't too long, just paste in as code here.

 

You will not be able to deploy to Google Play with 2018.3326. There is a good chance that you can't deploy to Apple with that version either (or won't in a few months if Apple follows it's normal pattern of requiring modern SDK support)

 

If you're on a Mac, don't close the build dialog, we will route the "adb logcat" output to the Corona console for you which can help filter out some of the noise.

 

Rob



[TOPIC: post.html]
#5

stalxerhd

[GLOBAL: userInfoPane.html]
stalxerhd
  • Enthusiast

  • 43 posts
  • Corona SDK

Hi Rob! I did not open a new topic, because my problems are local.

 

A month ago I finally migrate from Corona version 2018.3326 to newer version 2019.3559. My experience.

  1. The first problem was caused by the changed position and names of the files and folders that are creating when the project was first created. You can see for yourself how the new project folder looks like in 2018.3326 and in 2019.3559.

How did I do? I created a new project on versions 2018 and 2019. Then I compared the folders. After that, it took some time to correctly transfer all my files (only required for work) to folders of the 2019 engine version.

  1. Another problem (relevant now) is the Cyrillic filenames/foldernames inside project folder and sub-folders. For example, you have a "menu.lua" and create a duplicate "menu - копия.lua" and that’s it, the project will show a black screen after Corona logo, but the build successfully created and started. You still use "menu.lua", while "menu - копия.lua" is just a backup.
     
    So now I rename all duplicate files to English.



[topic_controls]
[/topic_controls]