Hi Giderosians,
We've released a new version,
2012.2.1: http://www.giderosmobile.com/downloadHere's the release notes:
http://www.giderosmobile.com/DevCenter/index.php/Release_notesAs you see, we immediately started preparing new versions after a stable release. Its numbering scheme will be like that:
2012.2.1
2012.2.2
2012.2.3
... etc
When we approach the stable release, it'll be numbered like that:
2012.8 RC (*)
2012.8
Thanks for your support, and have a nice weekend!Gorkem
(*) Edit: Removed "beta" phrase. Still to determine what wording to use there, to stress on the fact that we are in feature freeze and focus only on documentation, strings, templates, and bug fixes.
Comments
----
no idea why but chrome says it "appears malicious" after the download finishes and asks if I want to keep it or discard.
on this line:
android:configChanges="keyboard|keyboardHidden|orientation|screenSize"
Says error String types not allowed.
I know that mentioned config changes are not supported in Android 2.1, but Android 2.2 is selected as project target. So any ideas?
Can you install the latest sdk (version 4.0.3, API Level: 15) and try again? You should see Android 4.0.3 as shown in the screenshot.
From now on we'll try to use the latest sdk while maintaining the compatibility with 2.2. This is required to give support to some 3rd party libraries like admob without any problem.
Also you can open the file project.properties and change the line
target=android-15
to
target=android-8
to use Android 2.2 sdk.
Edit: if you change target as target=android-8, you should also delete screenSize from the line android:configChanges="keyboard|keyboardHidden|orientation|screenSize".
We're using nod32 with the latest database. But I rechecked the executable with online virus checkers and they all said it's clean. Maybe signing the executable solve this wrong warning. Let me look into this.
Thank you
Was the problem solved when you install Android SDK 4.0.3? Can you post an information here after you try?
Well, I'll post when I'll get it to work.
I might have misunderstood something, the way I thought it works, is that you need to target the lower SDK you want your app to work with (2.2), but now I see, that even if I target the latest SDK (4.0.3) it still works with android 2.2
So that you can use a feature that's introduced after 2.2 _with a check_ while ensuring the compatibility with 2.2.