Graphics 2.0 conversion questions

Solar2D Advanced Graphics
#1

Today, I tried to upload an update to one of my apps. Google gives me an error message to turn off debug mode in my android manifest and try again. As far as I know, there is no debug mode in Corona sdk. I got online and looked it up. Several other developers are having the same problem. The solution was to get the latest Corona sdk. Since I was downgraded from pro to free when My subscription expired, I had to remove the pro version and download the free version. As it turns out, it has Graphics 2.0, which requires a lot of revision in my app, or change my config.lua to use the graphics compatibility mode. I tested on the simulator and uploaded to my Droid Razr. Menu screen was garbage. I got rid of the compatibility statement and revised my main menu screen, tested it in the simulator and it looked fine. I then uploaded it to my Droid Razr to do a final test. The menu screen was still GARBAGE! My app has been completely destroyed! What the heck can I do now? My widgets don’t work, the display doesn’t work, except in the simulator. So far, I have lost money paying for two years of Corona sdk, and have it tripple in price in those two years. About time to change development tools.

Jerry

#2

Option 1.  Build with 1202, the last public build with the Graphics 1.0 engine.  You can get it here:  https://developer.coronalabs.com/downloads/archive

Option 2.  With public build 2076, put this line:

graphicsCompatibility = 1

in your config.lua at the same spot you have set your width and height.  This will fix most of your issue with Graphics 2.0.  If you are using the deprecated sprite engine, you will need to get the old sprite library from our GitHub repository.  See today’s blog post: http://www.coronalabs.com/blog/2013/11/20/tutorial-fast-migration-of-graphics-1-0-based-projects-to-graphics-2-0/ for more information.   Please note that some 3rd party libraries may still need to be adjusted, etc.

Either of those should get you going.  You should still throughly test your app before releasing it because we fixed a lot of bugs since 1202 and if you were using an older version before 1202 (given that you’re getting that Google Error, I suspect you were), there were significant bugs fixed then too that might change the behavior of your app.

Rob

#3

Thanks for the help. My app is now back in operation. I’ll try Graphics 2.0 on the next project.

#4

Hey Rob, I’m a pro subscriber, and I’m having the same debug signed apk issue.  

I’m seeing an access denied message when trying to download 1202.  I’m about to release an app I’ve been working on for many months, and would rather use the last Graphics 1.0 build.

#5

Hi @ryang, can you get the latest daily builds?  1260 has most of the bug fixes that went into 2076, and should be pretty close to a “stable” 1.0 engine as we have.

Rob

#6

Option 1.  Build with 1202, the last public build with the Graphics 1.0 engine.  You can get it here:  https://developer.coronalabs.com/downloads/archive

Option 2.  With public build 2076, put this line:

graphicsCompatibility = 1

in your config.lua at the same spot you have set your width and height.  This will fix most of your issue with Graphics 2.0.  If you are using the deprecated sprite engine, you will need to get the old sprite library from our GitHub repository.  See today’s blog post: http://www.coronalabs.com/blog/2013/11/20/tutorial-fast-migration-of-graphics-1-0-based-projects-to-graphics-2-0/ for more information.   Please note that some 3rd party libraries may still need to be adjusted, etc.

Either of those should get you going.  You should still throughly test your app before releasing it because we fixed a lot of bugs since 1202 and if you were using an older version before 1202 (given that you’re getting that Google Error, I suspect you were), there were significant bugs fixed then too that might change the behavior of your app.

Rob

#7

Thanks for the help. My app is now back in operation. I’ll try Graphics 2.0 on the next project.

#8

Hey Rob, I’m a pro subscriber, and I’m having the same debug signed apk issue.  

I’m seeing an access denied message when trying to download 1202.  I’m about to release an app I’ve been working on for many months, and would rather use the last Graphics 1.0 build.

#9

Hi @ryang, can you get the latest daily builds?  1260 has most of the bug fixes that went into 2076, and should be pretty close to a “stable” 1.0 engine as we have.

Rob