History API error: Invalid accessToken in request: xyz.F5UkPAOLTbMV4emxqgxzCb5... #1749
Assignees
Labels
bug
Something isn't working. It's clear that this does need to be fixed.
Comments
VeskeR
added
the
bug
|
Hi @Dajust, thanks for raising this issue. What environment are you running ably-js in? We've recently received a similar bug report for React Native (#1730). I think we didn't immediately fix it because the affected user was able to work around the issue, but it sounds like something we should be fixing as a priority. |
|
Hey @lawrence-forooghian, thanks for your response. Yes, I am on React Native. |
|
Thanks for the confirmation. We’re working on a fix. |
VeskeR
added a commit
that referenced
this issue
Apr 30, 2024
… possible This commit also ensures that whenever we access underlying ArrayBuffer via `TypedArray.prototype.buffer` we use `.slice()` method with corresponding `.byteOffset` and `.byteLength` properties to retrieve correct section of ArrayBuffer used by the TypedArray. Resolves #1730, Resolves #1749
VeskeR
added a commit
that referenced
this issue
Apr 30, 2024
… possible This commit also ensures that whenever we access underlying ArrayBuffer via `TypedArray.prototype.buffer` we use `.slice()` method with corresponding `.byteOffset` and `.byteLength` properties to retrieve correct section of ArrayBuffer used by the TypedArray. Resolves #1730, Resolves #1749
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since v2, I've been getting this invalid accessToken error whenever I call this
channel.history()API.Note that the same accessToken is used across all other APIs in my app and all work well, except the history API call, so yes, I think my API key is valid. I also tried with a newly created API key but to no avail.
┆Issue is synchronized with this Jira Task by Unito
The text was updated successfully, but these errors were encountered: