-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeError: env().platform.isTypedArray is not a function. (In 'env().platform.isTypedArray(a)', 'env().platform.isTypedArray' is undefined) #7273
Comments
use the previous version, for example @4.1.0 |
I am running into this issue with a react-native project. |
Experiencing the same issue with a new react-native project. Downgrading to 4.1.0 didn't help. |
How to fix it. Please let me know by someone.
…On Mon, Jan 16, 2023, 10:28 PM Rhys Camm ***@***.***> wrote:
Experiencing the same issue with a new react-native project.
—
Reply to this email directly, view it on GitHub
<#7273 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5H26K25QCTDLB3AS2M42WLWSV4ZRANCNFSM6AAAAAAT3C3LPI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Having done some digging, I think #7181 introduced this. I assume |
Edit: |
it works for me. I used the tsjs-node |
@huhm potentially I just needed to clear my metro cache and 4.1.0 would have worked. Though I think it's probably best to use the version |
After dowgrade ,getting same error bro |
4.1.0 fixed it for me - not using native react |
React Native Expo standalone workflow developers: you need to create a new development build. Downgrading to 3.7.0 worked for me after doing that |
Hi , thanks for mentioning it. I am facing the same issue. Although my application is in NodeJs environment is this going to work? Because downgrading and having its repercussion on other working models can also be an issue later. Please let me know |
Hey, so I am using Vite/React and downgrading to |
Hi, There are many examples failing on TFJS API web-site. |
I had the same problem whilst using Vite/React app. Fixed it by downgrading to TFJS to version 3.7.0. |
Also had same problem, but only when going to target page (containing tfjs logic) from another page. Reloading that page didn't produced that error. Using Nuxt3 / Vite. |
Also had same problem of running tests by CPU backend, downgrading to 4.1.0 worked. |
A new function, `isTypedArray` was added to the `platform` interface by tensorflow#7181 and first published in tfjs-core 4.2.0. This made 4.2.0 incompatible with earlier versions of backends that implemented `platform`, such as node and react-native. This change adds a fallback to the use of `isTypedArray` so earlier versions of platforms that don't implement `isTypedArray` will not throw an error. Note that the behavior may not be perfect, such as when running Jest tests in node. See tensorflow#7175 for more details and upgrade all @tensorflow scoped packages to ^4.2.0 to avoid this. Fixes tensorflow#7273
A new function, `isTypedArray` was added to the `platform` interface by tensorflow#7181 and first published in tfjs-core 4.2.0. This made 4.2.0 incompatible with earlier versions of backends that implemented `platform`, such as node and react-native. This change adds a fallback to the use of `isTypedArray` so earlier versions of platforms that don't implement `isTypedArray` will not throw an error. Note that the fallback behavior may not be perfect, such as when running Jest tests in node. See tensorflow#7175 for more details and upgrade all @tensorflow scoped packages to ^4.2.0 to avoid this. Fixes tensorflow#7273
Had same issue trying to add an lstm layer to an empty model using 4.2.0:
generated the following error
|
@Rhysjc which version of react native you are using because in my case 3..7.0. is incompatible with my react native version |
me too |
Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information
Describe the current behavior
Describe the expected behavior
Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/CodePen/any notebook.
Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.
The text was updated successfully, but these errors were encountered: