-
-
Notifications
You must be signed in to change notification settings - Fork 185
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
com.pusher.client.AuthorizationFailureException: java.io.FileNotFoundException: #25
Comments
Can you share your pusher configuration? |
I have the same problem Here's my Pusher config : static PusherClient? pusher;
static Channel? channel;
static Future<void> initPusher(String token, int userId) async {
PusherOptions options = new PusherOptions(
cluster: 'eu',
auth: new PusherAuth(
'https://url',
headers: {
'authentication': '$token',
},
),
);
try {
pusher = new PusherClient("APP_KEY", options,
enableLogging: true, autoConnect: false);
pusher?.connect();
channel = pusher?.subscribe("private-user" + '$userId');
}catch(e) {
}
After hours of debugging i managed that the pusher client is sending the previous token to the server. |
I have the same problem |
Do we have any solution on this problem? |
i suggest socket_io_client_2 |
Is it socket_io_client? I can't find socket_io_client_2 |
socket_io_client: ^2.0.0-beta.4-nullsafety.0 |
ok thanks |
I'm having exactly the same problem. Anyone solved the issue? |
This may solve your problem , the commit 32ec432. |
pusherclient has an instance stored in native code, even if you make a new instance of pusherclient, the native code still does null check on the native pusherclient instance. to fix this, first change lib/src/pusher/pusher_client.dart to not reuse the same instance.
then modify the native init func to not null check the native pusherclient instance. for android, for ios, |
if anyone still has this problem |
Hello I'm trying to authorize my pusher client but I keep getting this error: com.pusher.client.AuthorizationFailureException: java.io.FileNotFoundException: http://167.99.214.205/api/v1/broadcasting/auth.
Please what can I do?
The text was updated successfully, but these errors were encountered: