Updating Realtime channel options doesn’t update the options of its REST counterpart

[ikbalkaya]

Customer reports issues with channel history messages not being properly received

[Check internal discussion for details |https://ably-real-time.slack.com/archives/C8SPU4589/p1642403978004400]

The closest thing that points to that issue is in a log customer provided

Cannot construct ably realtime message from type: _Uint8ArrayView<…>

{{AblyWriter}} class in our iOS side of plugin has this method that is encoding paginated results back to the Flutter side

{code}
static AblyCodecEncoder encodePaginatedResult = ^NSMutableDictionary*(ARTPaginatedResult *const result) {
NSMutableDictionary<NSString *, NSObject *> dictionary = [[NSMutableDictionary alloc] init];
NSArray items = [result items];
if([items count] > 0){
UInt8 type = [AblyFlutterWriter getType:items[0]];
if(type != 0){
AblyCodecEncoder encoder = [AblyFlutterWriter getEncoder: [NSString stringWithFormat:@"%d", type]];
NSMutableArray *result = [NSMutableArray arrayWithCapacity:[items count]];
[items enumerateObjectsUsingBlock:^(id obj, NSUInteger idx, BOOL *stop) {
[result addObject: encoder(obj)];
}];
WRITE_VALUE(dictionary, TxPaginatedResult_type, [NSNumber numberWithInt:type]);
WRITE_VALUE(dictionary, TxPaginatedResult_items, result);
}
}
WRITE_VALUE(dictionary, TxPaginatedResult_hasNext, @([result hasNext]));

return dictionary;

};
{code}
Item types expected from that query are {{ARTMessage}}s. And those {{ARTMessage}}s have unspecified type of data properties which are likely causing the issues. Our integration tests do not raise any issues about this.