Closed tigerfarm closed 4 years ago
I made the change below, and now, when I join a channel that has a uniqueName, I can chat with users that are using my chat website application. My chat website application gives the channel a uniqueName value, the uniqueName is not nil.
...
builder?.withFriendlyName("${typ}_TestChannelF_${value}")
// ?.withUniqueName("${typ}_TestChannelU_${value}")
?.withUniqueName("${typ}_TestChannelF_${value}")
?.withType(type)
...
...
However, the Android Chat app still creates channels with the uniqueName as nil.
Hello @tigerfarm In the demo app we have two different menu items (see screenshot below):
Create public channel
- which shows dialog and creates a channel with friendlyName
entered by user and empty uniqueName
Create Pub Ch with options
- which doesn't show any dialogs, just creates a channel with random friendlyName
and random non-emptyuniqueName
like: Pub_TestChannelU_18
I've just double checked and both options works for me without any code modifications. If it still doesn't work for you - please attach detailed log. How to collect logs
No response, closing.
Description
After creating a new channel, I used a PHP program to list the channels. The UniqueName property was nil. This causes an issue in that users of my chat web application cannot exchange messages with this Android app because the web application expects a non-nill UniqueName. And, after briefing the code, it looks like you had intended to have the friendly and unique names the same.
Steps to Reproduce
Code (optional)
Expected Behavior
That channels are created with the uniqueName the same as the friendlyName which is the field value from the app's form.
Actual Behavior
That channels are created with the uniqueName as nil (null), the friendlyName has the correct field value from the app's form.
Reproduces how Often
Happens 100%.
Versions
All relevant version information for issue.
Android API is recent.
Android Device
Moto G Fast, Android 10.