We walked this back because of some regressions:
https://www.codenameone.com/blog/ios-migration-setback.html
This policy is enforced by Apple, however for compatibility with legacy
Apple is only enforcing it for apps built with a newer version of xcode.
Knowing Apple this version of xcode will
Our new xcode build servers use 6.0 so they should work. You can follow our
process of migrating to them in the blog.
To use them use the iphone_new target as explained here:
https://www.codenameone.com/blog/ios-server-migration-plan.html
Can you provide a link to the stack overflow question so I have context?
Make sure Java 8 is first in your system path. This is required for Eclipse.
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe from this group and
We have a fix for that build error which will be a part of the next update.
Notice that with the new Google play support you can include only location
support without including the ads support which is exactly why we
deprecated the global sweeping build switch.
See
If you have something specific in mind you can submit a pull request with
the javadoc changes you think are appropriate for this.
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving
I'm seeing the new "apple will disable HTTP" message in the simulator, and
your warning is correctly
reporting the http requests I make.
According to the cited blog post,
https://www.codenameone.com/blog/ios-http-urls.html
my builds should no longer work. But they do (at least IOS debug
This was posted on StackOverflow with no working answer so I thought I'd
try here:
Create a new project: Hello World (Bare Bones)
add new: Gui Builder, form, hit finish
error: Unresolved compilation problem: '<>' operator is not allowed for
source level below 1.7
java version is oracle's
OK forget that, im going mad now i think it was a false alarm. Not to
be confused with the screen flash when keyboard goes away.
On Monday, June 20, 2016 at 11:38:02 PM UTC+8, Gareth Murfin wrote:
>
> Ok not false alarm still happening, ARGH... but i cant see it on any
> device of my own.
Ok not false alarm still happening, ARGH... but i cant see it on any device
of my own.
On Monday, June 20, 2016 at 11:37:18 PM UTC+8, Gareth Murfin wrote:
>
> False alarm, it was a stray textarea, turned off the focusing and not
> happening now.
>
>
> On Monday, June 20, 2016 at 10:53:07 PM
False alarm, it was a stray textarea, turned off the focusing and not
happening now.
On Monday, June 20, 2016 at 10:53:07 PM UTC+8, Gareth Murfin wrote:
>
> Client is getting some odd stuff where the screen doubles up or is black,
> where keyboard would normally be:
>
>
>
>
Client is getting some odd stuff where the screen doubles up or is black,
where keyboard would normally be:
https://www.dropbox.com/s/x1tkqee21iwpbw7/f78b271a-04b2-433a-9d95-6719149fba6a.png?dl=0
and
https://www.dropbox.com/s/y6jd5rrx725e3ve/c5d592ec-ee23-41b4-806c-f35f73ed90fb.png?dl=0
As
Another suggestion in the referenced article was to build with android
gradle=false but that generated a build error.
I built with android.grade=false and android.includeGPlayServices=false
-compile:
[javac] Compiling 536 source files to
/tmp/build7034578418479870721xxx/AWMain/bin/classes
The referenced article says:
We transitioned the Google Play Services support to be on by default as
that is the common use case and makes API's like the location API far more
usable.
As a result 2.3.1 became the minimum OS version as imposed by Google.
This device is running 2.3.5 so it
13 matches
Mail list logo