Error: Backend name 'undefined' not found in registry
See original GitHub issueThis error shows up at 'console.log('Error tf.setBackend(): ‘, error);’ when I run the below code to run load posenet.
I used to use ‘tf.ready()’ and worked completely fine several weeks ago, but now this error shows up.
Please advise how to solve this.
Thank you.
Error: Backend name ‘undefined’ not found in registry
Versions are: expo --version 3.11.7 node --version v12.14.1 npm -version 6.13.4 @ tensorflow/tfjs-react-native@0.2.3 @tensorflow-models/posenet@2.2.1 @tensorflow/tfjs@1.7.2
import * as React from 'react';
import * as tf from '@tensorflow/tfjs';
import * as posenet from '@tensorflow-models/posenet';
export default class Notification extends React.Component {
inputTensorHeight = 200;
inputTensorWidth = 152;
async componentDidMount() {
await tf.setBackend().then( ref => {
console.log('--------- tf.setBackend');
}).catch(function(error) {
console.log('Error tf.setBackend(): ', error);
});
const posenetModel = await posenet.load({
architecture: 'MobileNetV1',
outputStride: 16,
inputResolution: { width: this.inputTensorWidth, height: this.inputTensorHeight },
multiplier: 0.75,
quantBytes: 2
}).then( ref => {
console.log('--------- posenet loaded.');
}).catch(function(error) {
console.log('Error posenet.load: ', error);
});
}
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Handpose tfjs Error - No backend found in registry
I had mistakenly come up with my own import line: import backend from '@tensorflow/tfjs-backend-webgl'. Correct version:.
Read more >Installing DSpace - Confluence Mobile - LYRASIS Wiki
Troubleshoot an error or find detailed error messages ... It cannot be run "standalone", as it requires a valid DSpace Backend to function....
Read more >Error messages - Resource Manager - Google Cloud
This document identifies some of the error codes and messages that Google APIs return. Specifically, the errors listed here are in the global,...
Read more >Troubleshooting - Unity - Manual
If you are trying to install a new package from the registry and it is not working, it might be due to permission...
Read more >npm packages in the Package Registry - GitLab Docs
npm publish returns npm ERR! 400 Bad Request. If you get this error, one of the following problems could be causing it. Package...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@sauceishere I think you are going to have to do a bit more digging to get help with debugging this. Without more detailed info about what encironment you are running in and what error is happening we won’t be able to effectively look into this.
If you aren’t seeing any errors from expo/javascript, try looking into the device logs to see what is output by the mobile device before the app shuts down. The react native docs have some more details on how to do this. Note you cannot use tfjs-react-native in a simulator.
It solved upon switch from Developer mode to Production mode on Expo. Thanks.