JS Bridge Error - Cannot read property SECURITY_LEVEL_ANY of undefined #192

fpauer · 2019-02-13T20:09:28Z

I've just got the latest versions 3.1.0 and 3.1.1 and unit tests started to fail

● Test suite failed to run

TypeError: Cannot read property 'SECURITY_LEVEL_ANY' of undefined



  at Object.<anonymous> (node_modules/react-native-keychain/index.js:6:26)

The text was updated successfully, but these errors were encountered:

fpauer · 2019-02-13T20:16:44Z

Added a global jest setup and mocked the entire Native Module:

jest.mock('react-native-keychain', () => ({
  setGenericPassword: jest.fn(),
  getGenericPassword: jest.fn(),
  resetGenericPassword: jest.fn()
}));

oblador · 2019-02-13T20:24:46Z

Ping @mandrigin. Not sure we want to fix this.

GraemeAllanBryce · 2019-02-20T11:35:55Z

This is breaking a production build for me. The dependency comes from @haskkor/react-native-pincode

I am confused because it appears to have been fine before.
What is the cause?

mandrigin · 2019-02-20T11:41:23Z

It looks like it doesn't load native modules for some reason. But if it doesn't then the whole library is kind of useless. I probably need to learn more how exactly you are building the app.

GraemeAllanBryce · 2019-02-20T11:44:57Z

It is a react-native app.
We use YARN for dependency management
Build in xCode or vsCode essentially comes dow to a react-native ios:build command

Thing is I have it all working fine on one branch with PINCode working fine and on another it is failing. Currently investigating yarn.lock but can't really see what the significant difference is between the two builds.

I will post back here once we nail it.

Anyy suggestions as to where we should be looking will be well received as, for now, its a puzzle!

mandrigin · 2019-02-20T11:50:55Z

Thanks!
This code was introduced in 3.1.0, so before that you can't even have this issue. Yarn should theoretically lock the dependencies...

vonovak · 2019-02-20T11:53:57Z

the cause is here

react-native-keychain/index.js

Line 5 in 01755de

export const SECURITY_LEVEL = Object.freeze({

you need to mock the constants exported from the native module for your JS tests

This does not explain though why builds suddenly stopped working for you. Are you sure you didn't upgrade?

marciok · 2019-02-26T15:17:30Z

jest.mock('react-native-keychain', () => ({
setGenericPassword: jest.fn(),
getGenericPassword: jest.fn(),
resetGenericPassword: jest.fn()
}));

Were you able to mock?? I tried to mock the whole class as you described, but it's still throwing the SECURITY_LEVEL_ANY error...

fpauer · 2019-02-26T16:40:13Z

@marciok Yes, but you need to include it in your jest setup file and in package.json define the setup file path.

"jest": {
    "preset": "react-native",
    .
    .
    .
    "setupFiles": [
      "./config/test/jest-setup.js"
    ]
  }

jest-setup.js

jest.autoMockOff();
jest.mock('react-native-keychain', () => ({
  setGenericPassword: jest.fn(),
  getGenericPassword: jest.fn(),
  resetGenericPassword: jest.fn()
}));

brianfoody · 2019-02-28T01:56:20Z

Thanks @fpauer that worked a treat. Legend!!

fbartho · 2019-02-28T20:07:30Z

I was able to mock this, sufficiently, in my jest's before all, using the following code:

RNNativeModules.RNKeychainManager = RNNativeModules.RNKeychainManager || {};

gberg1 · 2019-03-02T06:03:21Z

If I am getting this error merely when I import "import * as Keychain from 'react-native-keychain';"
into a react-native file after using Yarn for install and also running react-native link react-native-keychain what should I do?

gberg1 · 2019-03-03T20:21:59Z

Hey following up here. I get this error when I import "import * as Keychain from 'react-native-keychain';" into a react-native file. Ran yarn and react-native-link successfully. Not using Jest or anything. Can someone let me know what I need to fix this? Thanks! @oblador @fpauer @mandrigin

brianfoody · 2019-03-04T00:10:13Z

If you are getting it in a live app then you haven’t linked the module natively. react-native link react-native-keychain Or else link manually by following RN docs on it.

…

On Mon 4 Mar 2019 at 04:22, David Goldberg ***@***.***> wrote: Hey following up here. I get this error when I import "import * as Keychain from 'react-native-keychain';" into a react-native file. Ran yarn and react-native-link successfully. Not using Jest or anything. Can someone let me know what I need to fix this? Thanks! @oblador <https://github.com/oblador> @fpauer <https://github.com/fpauer> @mandrigin <https://github.com/mandrigin> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#192 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB1mZd7nYxFmqdBRmzbw7OYnmqDr6Kifks5vTC7ogaJpZM4a6LZP> .

gberg1 · 2019-03-04T03:07:40Z

@brianfoody thanks I did successfully link via react-native link react-native-keychain before getting the error. I was able to manually link and the error went away. I'm unblocked thank you.

In general I assume its best practice to use cocoa pods instead of dragging the workspace file into the Libraries folder manually and adding the .a module to Link Binary with Libraries correct?

brianfoody · 2019-03-04T03:19:05Z

I try to avoid pods if I can and just use react native link. It’s not always perfect though. The manual process does feel a bit wrong but at least it’s easily fixed. When pods breaks stuff it’s always a nightmare for me.

…

On Mon 4 Mar 2019 at 11:07, David Goldberg ***@***.***> wrote: @brianfoody <https://github.com/brianfoody> thanks I did successfully link via react-native link react-native-keychain before getting the error. I was able to manually link and the error went away. I'm unblocked thank you. In general I assume its best practice to use cocoa pods instead of dragging the workspace file into the Libraries folder manually and adding the .a module to Link Binary with Libraries correct? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#192 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB1mZeL8dpM023KLhZQiuseFgwCPFTrhks5vTI39gaJpZM4a6LZP> .

brianfoody · 2019-03-04T03:19:50Z

Good to hear you are unblocked, I know the pain of getting blocked on these things only too well.

…

On Mon 4 Mar 2019 at 11:18, Brian Foody ***@***.***> wrote: I try to avoid pods if I can and just use react native link. It’s not always perfect though. The manual process does feel a bit wrong but at least it’s easily fixed. When pods breaks stuff it’s always a nightmare for me. On Mon 4 Mar 2019 at 11:07, David Goldberg ***@***.***> wrote: > @brianfoody <https://github.com/brianfoody> thanks I did successfully > link via react-native link react-native-keychain before getting the error. > I was able to manually link and the error went away. I'm unblocked thank > you. > > In general I assume its best practice to use cocoa pods instead of > dragging the workspace file into the Libraries folder manually and adding > the .a module to Link Binary with Libraries correct? > > — > You are receiving this because you were mentioned. > > > Reply to this email directly, view it on GitHub > <#192 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AB1mZeL8dpM023KLhZQiuseFgwCPFTrhks5vTI39gaJpZM4a6LZP> > . >

fbartho · 2019-05-16T22:47:29Z

As mentioned above, we are also exhibiting this issue when in a Jest context. It'd be awesome if that mock solution was in a file in this node module.

Other libraries going through this:

react-native-reanimated: Add a mock implementation for test runners software-mansion/react-native-reanimated#276 (Not coupled to Jest!)
react-native-gesture-handler: Docs jestSetup.js mock file -- Not sure but I think this is sort of jest specific.

If anybody wants to submit a PR, I recommend doing something like the above examples?

liranhershko · 2019-05-20T09:41:04Z

I solved the Cannot read property 'SECURITY_LEVEL_ANY' of undefined error by placing a mock file react-native-keychain.js under __mocks__ folder at the root of the app.
The file's content is simply

const RNKeychainManager = {
  SECURITY_LEVEL_ANY: "SECURITY_LEVEL_ANY",
  SECURITY_LEVEL_SECURE_SOFTWARE: "SECURITY_LEVEL_SECURE_SOFTWARE",
  SECURITY_LEVEL_SECURE_HARDWARE: "SECURITY_LEVEL_SECURE_HARDWARE"
};

export default RNKeychainManager;

Unfortunately all other methods described here didn’t work.

vinaygoyal20 · 2019-06-08T06:50:00Z

If you are getting it in a live app then you haven’t linked the module natively. react-native link react-native-keychain Or else link manually by following RN docs on it.
…
On Mon 4 Mar 2019 at 04:22, David Goldberg @.***> wrote: Hey following up here. I get this error when I import "import * as Keychain from 'react-native-keychain';" into a react-native file. Ran yarn and react-native-link successfully. Not using Jest or anything. Can someone let me know what I need to fix this? Thanks! @oblador https://github.com/oblador @fpauer https://github.com/fpauer @mandrigin https://github.com/mandrigin — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#192 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AB1mZd7nYxFmqdBRmzbw7OYnmqDr6Kifks5vTC7ogaJpZM4a6LZP .

Thanks @brianfoody linking manually worked for me

zackdotcomputer · 2019-07-02T19:53:55Z

Though I agree with @fbartho that the end goal would be a functional mock that could be imported by developers for testing, I think a good no-effort stopgap would be to surface @fpauer's solution in the README, which is what several other packages also do to help out RN + Jest users. I created a quick PR to add a section with the instructions for how to mock and (hopefully) unbreak the build of anyone else affected by this.

fpauer · 2019-07-02T20:52:37Z

@genuinezack another approach to mock the whole package is:

1 - Create a folder in src called __mocks__
2 - Create a folder for the package, in this case react-native-keychain
3 - Create a index.js file to mocks all methods

/src/__mocks/react-native-keychain/index.js

export default {
  setGenericPassword: jest.fn(),
  getGenericPassword: jest.fn(),
  resetGenericPassword: jest.fn()
}

In that way you dont need to define jest setup files

zackdotcomputer · 2019-07-02T20:55:58Z

Yup! However, the project I'm helping out with already had a setup file (for mocking local data & API endpoints) and didn't have a __mocks__ directory, so I went with your first solution personally. I'll update the PR to mention that solution as well.

fahry-mohammed · 2021-07-02T09:40:30Z

@fpauer I have the same code as you suggest but the test not working and indicates the following error:
TypeError: Cannot read property 'AES' of undefined

Using the current latest version of keychain: react-native-keychain": "^7.0.0

here is the code which I am using:

Defining the type globally:

const CONFIG = {
  storage: ReactNativeKeychain.STORAGE_TYPE.AES
}

Then use it for all places like the following:

export async function save(username: string, password: string, server?: string) {
  if (server) {
    await ReactNativeKeychain.setInternetCredentials(server, username, password, CONFIG)
    return true
  } else {
    return ReactNativeKeychain.setGenericPassword(username, password, CONFIG)
  }
}

Having moke on setup file:

jest.autoMockOff()
jest.mock('react-native-keychain', () => ({
  setGenericPassword: jest.fn(),
  getGenericPassword: jest.fn(),
  setInternetCredentials: jest.fn(),
  resetGenericPassword: jest.fn(),
  resetInternetCredentials: jest.fn(),
}))

Mentioned on package json file too:

"setupFiles": [
      "<rootDir>/node_modules/react-native/jest/setup.js",
      "<rootDir>/test/setup.ts"
    ],

Please let me know whether I am making any mistakes...
Thank you

codewithraqib · 2021-07-16T11:57:42Z

i reset the cache and some other stuff watchman watch-del-all && rm -f yarn.lock && rm -rf node_modules && yarn && yarn start --reset-cache

and closed the debug mode and it is working.

I suppose this happens if you are working on more than one projects at a time in same machine

vonovak mentioned this issue Jul 18, 2019

Update mocking #230

Merged

oblador closed this as completed in #230 Sep 7, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

JS Bridge Error - Cannot read property SECURITY_LEVEL_ANY of undefined #192

JS Bridge Error - Cannot read property SECURITY_LEVEL_ANY of undefined #192

fpauer commented Feb 13, 2019

fpauer commented Feb 13, 2019 •

edited

Loading

oblador commented Feb 13, 2019

GraemeAllanBryce commented Feb 20, 2019

mandrigin commented Feb 20, 2019

GraemeAllanBryce commented Feb 20, 2019

mandrigin commented Feb 20, 2019

vonovak commented Feb 20, 2019 •

edited

Loading

marciok commented Feb 26, 2019

fpauer commented Feb 26, 2019

brianfoody commented Feb 28, 2019

fbartho commented Feb 28, 2019

gberg1 commented Mar 2, 2019 •

edited

Loading

gberg1 commented Mar 3, 2019

brianfoody commented Mar 4, 2019 via email

gberg1 commented Mar 4, 2019

brianfoody commented Mar 4, 2019 via email

brianfoody commented Mar 4, 2019 via email

fbartho commented May 16, 2019 •

edited

Loading

liranhershko commented May 20, 2019 •

edited

Loading

vinaygoyal20 commented Jun 8, 2019

zackdotcomputer commented Jul 2, 2019

fpauer commented Jul 2, 2019 •

edited

Loading

zackdotcomputer commented Jul 2, 2019

fahry-mohammed commented Jul 2, 2021 •

edited

Loading

codewithraqib commented Jul 16, 2021

JS Bridge Error - Cannot read property SECURITY_LEVEL_ANY of undefined #192

JS Bridge Error - Cannot read property SECURITY_LEVEL_ANY of undefined #192

Comments

fpauer commented Feb 13, 2019

fpauer commented Feb 13, 2019 • edited Loading

oblador commented Feb 13, 2019

GraemeAllanBryce commented Feb 20, 2019

mandrigin commented Feb 20, 2019

GraemeAllanBryce commented Feb 20, 2019

mandrigin commented Feb 20, 2019

vonovak commented Feb 20, 2019 • edited Loading

marciok commented Feb 26, 2019

fpauer commented Feb 26, 2019

brianfoody commented Feb 28, 2019

fbartho commented Feb 28, 2019

gberg1 commented Mar 2, 2019 • edited Loading

gberg1 commented Mar 3, 2019

brianfoody commented Mar 4, 2019 via email

gberg1 commented Mar 4, 2019

brianfoody commented Mar 4, 2019 via email

brianfoody commented Mar 4, 2019 via email

fbartho commented May 16, 2019 • edited Loading

Other libraries going through this:

liranhershko commented May 20, 2019 • edited Loading

vinaygoyal20 commented Jun 8, 2019

zackdotcomputer commented Jul 2, 2019

fpauer commented Jul 2, 2019 • edited Loading

zackdotcomputer commented Jul 2, 2019

fahry-mohammed commented Jul 2, 2021 • edited Loading

codewithraqib commented Jul 16, 2021

fpauer commented Feb 13, 2019 •

edited

Loading

vonovak commented Feb 20, 2019 •

edited

Loading

gberg1 commented Mar 2, 2019 •

edited

Loading

fbartho commented May 16, 2019 •

edited

Loading

liranhershko commented May 20, 2019 •

edited

Loading

fpauer commented Jul 2, 2019 •

edited

Loading

fahry-mohammed commented Jul 2, 2021 •

edited

Loading