You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Demo QuickStart, the documents refers to the need to set up a token server. https://docs.agora.io/en/flexible-classroom/get-started?platform=ios#references in the references. It's not clear that as a PaaS solution flexible classroom has a token server baked in, and all the developer needs to do as add their AppID and Cert information in the .env file, and they should be all set.
In the understand the tech section, https://docs.agora.io/en/flexible-classroom/get-started/?platform=web#understand-the-tech, it also refers to the need to generate an RTM token for signaling, and links to the standard practice of creating an RTM token / RTM token server. Again, this should be automatically taken care of in FCR. The document also don't talk about the RTC token which, I had encountered an error when trying to set up FCR with a bad RTC token. There is also confusion around RTC vs RTM token.
Ideally, FCR should work without the need to worry about the tokens, and it should be clear that the other token management docs that are available do do not apply to FCR.
The text was updated successfully, but these errors were encountered:
In the Demo QuickStart, the documents refers to the need to set up a token server. https://docs.agora.io/en/flexible-classroom/get-started?platform=ios#references in the references. It's not clear that as a PaaS solution flexible classroom has a token server baked in, and all the developer needs to do as add their AppID and Cert information in the .env file, and they should be all set.
In the understand the tech section, https://docs.agora.io/en/flexible-classroom/get-started/?platform=web#understand-the-tech, it also refers to the need to generate an RTM token for signaling, and links to the standard practice of creating an RTM token / RTM token server. Again, this should be automatically taken care of in FCR. The document also don't talk about the RTC token which, I had encountered an error when trying to set up FCR with a bad RTC token. There is also confusion around RTC vs RTM token.
Ideally, FCR should work without the need to worry about the tokens, and it should be clear that the other token management docs that are available do do not apply to FCR.
The text was updated successfully, but these errors were encountered: