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
For some reason, int64 is returned as string from the Telegram server.
Adjust the generator to generate string type for int64 fields.
This fixesi-Naji#15.
For some reason, int64 is returned as string from the Telegram server.
Adjust the generator to generate string type for int64 fields.
This fixesi-Naji#15.
For some reason, int64 is returned as string from the Telegram server.
Adjust the generator to generate string type for int64 fields.
This fixesi-Naji#15.
There seems to be some inconsistency between the types returned by the Telegram server and the definition. For example, I got the following error:
According to the API definition (https://github.com/i-Naji/tdlib/blob/master/data/td_api.tl#L315 as well as upstream https://github.com/tdlib/td/blob/master/td/generate/scheme/td_api.tl#L315),
ProfilePhoto.id
is an int. But I'm getting the error above. I'm wondering whether the upstream definition is out of date with the Telegram server for some reason. BTW, there are quite some types that have the string to int mismatch issue when running the example in this repo.The text was updated successfully, but these errors were encountered: