Guillermo Rodríguez

With android-priority-jobqueue 2.0.1 and Proguard v5.3.3, the build fails with this: ``` Warning: com.birbit.android.jobqueue.scheduling.GcmJobSchedulerService: can't find superclass or interface com.google.android.gms.gcm.GcmTaskService Warning: com.birbit.android.jobqueue.scheduling.GcmJobSchedulerService: can't find referenced class com.google.android.gms.gcm.GcmTaskService Warning: com.birbit.android.jobqueue.scheduling.GcmJobSchedulerService: can't...

BTW I did not need to add `-keep interface com.birbit.android.jobqueue.** { *; }` ; my build does not fail if I leave that out.

Just came across this. See my comment in issue #1337. It was closed as a dupe of #675, which only added support for response code 100, but not for 102...

Yes I know, but it is invisible in practice for most users since it is not linked anywhere.

Revisiting this issue. The bright and shiny new site was implemented during April/May 2021. However http://robovm.mobidevelop.com/ still shows the old, outdated site. I would not be surprised if new users...

> @guillerodriguez it's linked here, first thing on the Github page. That is the **old** site. Which very nicely shows my point: the new site is basically invisible.

@WillCalderwood This should now be fixed in RoboVM 2.3.13 via #564 (your original report mentions this happened in "2.3.13" but I assume that was a snapshot and not the final...

@liZe PR #351 implement this feature.

@liZe Ping

I have a touch controller that reports events at a very high rate (more than 200 per second). This is creating an unnecessary load in the system so I am...