-
Notifications
You must be signed in to change notification settings - Fork 36
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
About RTM engine init and Message receive. #33
Comments
is the token null? have you turned on token? |
I have this issue on iPhone 11 14.4 too. I don't send token as soon as my app is in testing mode. |
Thanks yeah, I've tried with both a temp token (in testing mode) and a null token. Works on earlier iOS versions but not on newer versions. Again, I've only tested iOS 14.0 and 14.4.1 so I'm not sure at what version this may have started occurring. Is it working for you @plutoless ? |
Sorry to reply you so late
|
Yeah for whatever reason on the newer iOS versions logging into RTMEngine just returns Error Code 9 for timeout. Doesn't specify why. The other two return Error Code 102 due to not being logged in =/. Any ideas? |
Maybe you should check you fireware? |
I could be wrong but I don't think it has to do with firewalls? This seems to be a problem only with iOS 14.4+. Logging in (both |
Do you mean that iOS can't login by use rtm sdk? |
Yes, correct. This RTM SDK cannot login on iOS 14.4.1. I've tried on two separate iPhones. I can confirm it works on earlier iOS version (14.0.0). I'm familiar with the docs and followed the procedures properly. Can you verify that you are able to login to the RTM SDK on iOS version 14.4.1? |
Let me give that a try tomorrow! Thanks for the help. Seems to be my issue then for sure. |
@RoJoHub It worked for me this morning! I'm not positive what fixed it but these are the changes I made.
Thanks for your help everyone! I'll continue to monitor and try to understand what initially caused the problem. |
Can confirm that creating a project without token worked |
Wondering how we might get the token to work since we'd probably want that in production. |
You may need to consult a backend. |
Yeah, can anybody confirm that they got it working on iOs 14.4 with token? |
I have tried it with backend token generation as well as temp tokens via console, neither worked. Would also like to know if someone got it working on iOS 14.4+ w/ token. |
This involves the authentication mechanism, it is recommended to submit a ticket on the agora official website. |
Why isn't it linked to agora-react-native-rtm library if it's not working with token only on iPhone 14.4? Android however works |
I would like to know that too. I did submit a ticket directly in the Agora console regarding implementation of token based RTM logins so I'll reply here with what they say. |
This has been resolved for me although I didn't necessarily do anything differently. Can't explain why it was happening before or how I managed to fix it. May want to leave this open to see if others experience the same issues :) @t3hfx is yours still timing out? |
Any update here? I cannot login via token as described above. |
Hey there. I'm using
agora-react-native-rtm
to handle user join subscriptions for audio broadcasting. It works fine on simulator & my iPhone X on iOS 14 (the users list updates & all events are properly fired off). However, on my iPhone 12 Pro running iOS 14.4.1 thertmEngine
events fail to fire for seemingly no reason. They simply return a generic Error object w/ no message.rtcEngine
works properly and I'm able to connect + hear audio coming from the iPhone 12 Pro, so just anrtmEngine
issue here. Any ideas on what might be going wrong?Errors (as you can see I tried logging the
message
andname
of the first Error object but it doesn't contain any useful info):Initialize method for RTM:
Here's a snippet of the
startCall
method. The firstawait
for rtcEngine succeeds but the subsequent 3awaits
for rtmEngine fail (only on iPhone 12 Pro running iOS 14.4.1).P.S.
agora-react-native-rtm
is on version^1.2.2-alpha.6
andreact-native-agora
is^3.3.1
.Thanks!
The text was updated successfully, but these errors were encountered: