They are still assigned for the 3.8 milestone. I'm not sure about the
status of those pull requests.
The main issue with building pieces etc. is state/security. We don't store
anything in the servers and wipe them clean. This is essential. It also
helps with consistent repeatable results.
Hi,
the Parse4cn1 Logger is invoked when the app is suspended and Display calls
might fail. In background tasks you can't invoke most of the Display calls.
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe from this
I have a couple push requests still pending that will affect this phase of
the build favorably.
I'd love to be able to do my builds in a more modular way.
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe from this
Sorry guys,
I forgot to mention this is only happenning in the Android version of the
app, iOS is working normally.
On Friday, January 5, 2018 at 11:00:38 AM UTC-5, Mario Barón wrote:
>
> Hi guys,
>
> I'm getting a rather weird error when receiving push notifications through
> Parse using
Hi guys,
I'm getting a rather weird error when receiving push notifications through
Parse using the parse4cn1 library:
01-05 10:28:20.143 2539-2539/? W/GCM-DMM: broadcast intent callback:
result=CANCELLED forIntent { act=com.google.android.c2dm.intent.RECEIVE
flg=0x1000
