-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android lambda exceptions for client #246
Comments
Have you considered using the WebSocket client? It'll be simpler than getting a bunch of Java 8 libraries to work (stably) in Dalvik. |
sijie
pushed a commit
to sijie/pulsar
that referenced
this issue
Mar 4, 2018
* removing snapshotting * cleaning up
the minimal requirement for java is java8. and there is a websocket proxy, so you can use websocket api. |
hangc0276
pushed a commit
to hangc0276/pulsar
that referenced
this issue
May 26, 2021
Fixes apache#312 These tests were ignored temporarily just because they rely on the outdated methods that convert between MessageId and Kafka offset. So this PR fixes these tests and deletes these outdated methods. The exception is testBrokerRespectsPartitionsOrderAndSizeLimits, it's a broken test that is easily affected by some params. apache#287 and apache#246 are tracking the test.
nicoloboschi
pushed a commit
to nicoloboschi/pulsar
that referenced
this issue
May 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behavior
I have an android app, in which I have added Pulsar Client with gradle. It compiles fine with these additional settings in build.gradle file:
Actual behavior
But when I run the app, I get the following exceptions and it fails:
How can we reproduce the issue
Can it be because Android does not accept lambdas by default ? How can I achieve Pulsar Client to run in Android ?
Is there a 1.7 version compiled version of client jars ?
System configuration
Pulsar version: 1.16
The text was updated successfully, but these errors were encountered: