Some bug with the build .280

Hi,
My code that works perfectly fine with .265 breaks on .280, I cannot pin point what causes that crash.

The reason for daily builds is to check for bugs, where do we report these? Would you need some code to see and replicate the same? or some crash logs, etc??

cheers,

Jayant C Varma [import]uid: 3826 topic_id: 6117 reply_id: 306117[/import]

Where can I get 280? [import]uid: 9371 topic_id: 6117 reply_id: 20941[/import]

There should be a bug submission form coming up in a few days

if it breaks on 280 - make sure you have 268 to go back to. -
do you have a crash log or a message that we can see?
c. [import]uid: 24 topic_id: 6117 reply_id: 20981[/import]

Where do we get build 280? [import]uid: 7175 topic_id: 6117 reply_id: 20993[/import]

280 doesnt work for me either. Just a blank screen, no errors in adb logcat…

When I touch the screen I get a series of touch events, but thats about it. Similar in 277 actually. I’m still using 243 since 268 has the file folder bug, where I need to put all my resources in the root folder

I/ActivityManager( 183): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.tiler.kamsgames/.MyCoronaActivity bnds=[384,716][480,800] } from pid 269  
I/WindowManager( 183): Setting rotation to 1, animFlags=1  
I/ActivityManager( 183): Config changed: { scale=1.0 imsi=234/30 loc=en\_GB touch=3 keys=1/1/2 nav=3/1 orien=2 layout=34 uiMode=17 seq=10}  
I/dalvikvm( 256): Jit: resizing JitTable from 4096 to 8192  
I/System.out( 3444): Corona version = Corona/Android/1.0  
D/WIDGET ( 2491): Updating all widgets  
D/WIDGET ( 2491): updatin widget with id 34  
I/ActivityManager( 183): Displayed com.tiler.kamsgames/.MyCoronaActivity: +169ms  
I/System.out( 2491): DSFDFSD=Interesting Times : The New Yorker  
I/SoundDecoder( 3444): ALL MPG123 DECODERS:  
I/System.out( 2491): WIDGET CACHE STORIES=20  
I/SoundDecoder( 3444): generic  
I/SoundDecoder( 3444):   
I/SoundDecoder( 3444): SUPPORTED MPG123 DECODERS:  
I/SoundDecoder( 3444): generic  
I/SoundDecoder( 3444):   
D/dalvikvm( 3444): GC\_CONCURRENT freed 537K, 59% free 2797K/6727K, external 1625K/2137K, paused 2ms+2ms  
W/IInputConnectionWrapper( 269): showStatusIcon on inactive InputConnection  
D/dalvikvm( 269): GC\_EXPLICIT freed 350K, 52% free 4141K/8583K, external 8156K/8872K, paused 1086ms  
D/dalvikvm( 183): GC\_EXPLICIT freed 808K, 53% free 6433K/13575K, external 6396K/7926K, paused 130ms  
D/dalvikvm( 3444): GC\_CONCURRENT freed 504K, 59% free 2808K/6727K, external 1625K/2137K, paused 1ms+3ms  
D/dalvikvm( 3444): GC\_CONCURRENT freed 514K, 59% free 2808K/6727K, external 1625K/2137K, paused 2ms+2ms  
D/dalvikvm( 3444): GC\_CONCURRENT freed 526K, 59% free 2808K/6727K, external 1625K/2137K, paused 3ms+3ms  
D/dalvikvm( 3322): GC\_EXPLICIT freed 54K, 53% free 2539K/5379K, external 1625K/2137K, paused 522ms  
D/dalvikvm( 3444): GC\_CONCURRENT freed 514K, 59% free 2820K/6727K, external 1625K/2137K, paused 2ms+6ms  
D/dalvikvm( 363): GC\_EXPLICIT freed 165K, 58% free 4290K/10119K, external 2994K/3740K, paused 90ms  
D/dalvikvm( 269): GC\_EXPLICIT freed 151K, 53% free 4083K/8583K, external 7599K/8872K, paused 55ms  
V/Corona ( 3444): \*\*\*\*\* onTouchEvent(0) \*\*\*\*\*  
V/Corona ( 3444): \*\*\*\*\*\* ACTION\_DOWN: CLEARING \*\*\*\*\*\*\*\*  
V/Corona ( 3444): \*\*\*\*\* onTouchEvent(2) \*\*\*\*\*  
V/Corona ( 3444): \*\*\*\*\* onTouchEvent(2) \*\*\*\*\*  
V/Corona ( 3444): \*\*\*\*\* onTouchEvent(2) \*\*\*\*\*  
V/Corona ( 3444): \*\*\*\*\* onTouchEvent(2) \*\*\*\*\*  
V/Corona ( 3444): \*\*\*\*\* onTouchEvent(2) \*\*\*\*\*  
V/Corona ( 3444): \*\*\*\*\* onTouchEvent(2) \*\*\*\*\*  
V/Corona ( 3444): \*\*\*\*\* onTouchEvent(2) \*\*\*\*\*  
V/Corona ( 3444): \*\*\*\*\* onTouchEvent(2) \*\*\*\*\*  

[import]uid: 8872 topic_id: 6117 reply_id: 21010[/import]

You are just trying to build Android?

C [import]uid: 24 topic_id: 6117 reply_id: 21081[/import]

Yeah, all android right now. [import]uid: 8872 topic_id: 6117 reply_id: 21082[/import]

Yes, where is .280 and daily build link please? [import]uid: 8496 topic_id: 6117 reply_id: 21144[/import]

Same here. 280 runs nicely in simulator and iOS emulator, but device builds all result in a blank screen with no activity.

268 builds the same app just fine. [import]uid: 11393 topic_id: 6117 reply_id: 21213[/import]

@bedhoudin Interesting – [import]uid: 24 topic_id: 6117 reply_id: 21288[/import]

Yes, me too iOS build 268 compiles and runs fine on device

Then 280 build - loading screen and then goes blank and does not run

Then I tried 295 build - same thing as build 280 , blank screen

Note: I am using the Director.lua class to switch between .lua files

Everything else is pretty standard.

Also, I have moved all my resources into Root folder so I can use build 268 (so it is not a sub-folder issue)

Just wanted to give you an update that the two latest build drops do not run on either device (iPhone or Android)

I am still using Build 268

Thanks, [import]uid: 10965 topic_id: 6117 reply_id: 22233[/import]

any code assets you can share? I am using the latest and no issue for me

c [import]uid: 24 topic_id: 6117 reply_id: 22250[/import]

I went back and tested them all again. On android at least:

268 - Works fine, Doesnt work if any resources are in a subfolder.
280 - Spams logcat wit onTouch event logs, but works. Doesnt work if any resources are in a subfolder.

295 - Seems to work fine. Doesnt work if any resources are in a sub folder

One thing I noticed on all of them is a heap overflow on start. I dont have the log handy, but it says something like heap overflow, requested 105900, max size 104900

[import]uid: 8872 topic_id: 6117 reply_id: 22256[/import]

is this android issue only or ios or both?

C [import]uid: 24 topic_id: 6117 reply_id: 22261[/import]

I’m relatively sure the resource subfolder thing is an android only issue, otherwise there would be a lot more complaints about it.

The black screen on daily builds isn’t happening for me on android if the resources are all in root, either thats an iOS issue only, or the issues ssinger is having are with his particular app. [import]uid: 8872 topic_id: 6117 reply_id: 22263[/import]