- Ably FAQs
- Realtime API and client libraries
- Common issues
-
Account billing and packages
-
General
-
Realtime API and client libraries
-
Troubleshooting
-
Channels
-
REST API and client libraries
-
Ably error codes
-
Account and app setup and configuration
-
Ably architecture, transports, and security
-
Performance and Redundancy
-
Push Notifications
-
Integrations
-
Migrating to Ably from an existing service
ClassNotFoundException when using Proguard with ably-java
If using Proguard with the Java client library, the following flags should avoid ClassNotFoundException issues:
-keep class io.ably.lib.** { *; } -keep class org.msgpack.core.** { *; }