Stream<RealtimeMessage> subscription returns null everytime.

I have a working stream for one of my collections, but setting up the second one never works. Logging for my first stream that works look like:

First Stream: Instance of '_BroadcastStream<RealtimeMessage>'
I/flutter (24668): AppwriteRealtime: Allow self-signed certificate
I/flutter (24668): subscription: wss://cloud.appwrite.io/v1/realtime?project=************

I can see the subscription activated and it works as intended. On the second one, I am following the exact same process and just feeding a different collection:

@override
  Stream<RealtimeMessage> getLatestProfile() {
    final stream = _realTime.subscribe([
      'databases.${AppWriteConstants.databaseId}.collections.${AppWriteConstants.usersCollectionId}.documents'
    ]).stream;
    print('Stream $stream');
    return stream;
  }

Second Stream: Instance of '_BroadcastStream<RealtimeMessage>'
I/flutter (24668): AppwriteRealtime: Allow self-signed certificate
I/flutter (24668): subscription: null

The subscription just returns null everytime. Not sure if it matters, but I have confirmed both collections have the same permissions, and ensured I don't have any typos and the database/collection Ids are infact correct, I've even tried hard coding them.

FYI, it's best to wrap code in backticks to format a bit nicer. You can use 1 backtick for inline code (https://www.markdownguide.org/basic-syntax/#code) and 3 backticks for multiline code (https://www.markdownguide.org/extended-syntax/#syntax-highlighting.

There's a bug with the flutter SDK and making multiple subscribe calls

https://github.com/appwrite/sdk-for-flutter/issues/156

It looks like this has been an active bug since June, half a year is quite some time. I tried the work around of created a second instance and that did solve the problem, so it's definitely this issue.

What was your work around. I myself am struggling with this

I posted the solution, it's just to create a second instance. In my case, I have like 5 different instances now that I have numbered sort of annoying but it works.

Odd, even separate instances are not particularly reliable for me. I chalked it up to single websocket being disrupted if I add new instances so I currently have just one that includes everything I want yo monitor and if(event) everywhere I use the trigger..