-
Notifications
You must be signed in to change notification settings - Fork 3
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
customObject implementation #182
Conversation
|
||
project 'PowerAuth' | ||
|
||
target 'PowerAuth' do | ||
config = use_native_modules! | ||
use_react_native!( | ||
:path => config[:reactNativePath] | ||
:path => config[:reactNativePath], | ||
:hermes_enabled => false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just comment here: this causes problem with the latest release and our integration and is only for our internal purposes, so disabled.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you describe the source of the problems? I was using "testapp" project only, for the development workflows. If I remember this correctly, then opening the standalone project was pain in the ass in recent RN stack, for both platforms. Using the "testapp" project was much better.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hermes is a Facebook-made javascript engine tailored for react native and brings faster startup times.
Basically, for a final build (when compiled), it improves performance but also brings many dependencies that need to be maintained and fixed when broken.
Since we use this only for our test projects and test apps, it's not needed.
Test projects for iOS and the test app still work but with the default js engine, not the Hermes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code looks OK. Please add docs/Version-2.5.md
that describe possible migration instructions, even if there's none.
|
||
project 'PowerAuth' | ||
|
||
target 'PowerAuth' do | ||
config = use_native_modules! | ||
use_react_native!( | ||
:path => config[:reactNativePath] | ||
:path => config[:reactNativePath], | ||
:hermes_enabled => false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you describe the source of the problems? I was using "testapp" project only, for the development workflows. If I remember this correctly, then opening the standalone project was pain in the ass in recent RN stack, for both platforms. Using the "testapp" project was much better.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks OK
The issue was addressed and confirmed by the 2nd reviewer and the customer is waiting for the release.
Resolves #181
react-native
version.This change should be released as 2.5.0
react-native-powerauth-mobile-sdk-2.5.0.tgz