During development, I found that if you do not use the correct Identity (I was just using a string) you will receive a cross-origin error in react development mode.
Then when I launch the app (see attached). Interestingly enough, when I converted the hook to use the v1 api (window.fin.desktop.) the cross origin error went away (course the Identity was wrong so it didn't work anyway).
During development, I found that if you do not use the correct Identity (I was just using a string) you will receive a cross-origin error in react development mode.
Example: Inside my component:
Then when I launch the app (see attached). Interestingly enough, when I converted the hook to use the v1 api (window.fin.desktop.) the cross origin error went away (course the Identity was wrong so it didn't work anyway).
Just thought I would pass this along. -Darren