Skip to content
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.

Sign up for GitHub

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

Jump to bottom

os_lib_call implementation is different from BOLOS' one #416

Open
yogh333 opened this issue Aug 10, 2023 · 0 comments
Open

os_lib_call implementation is different from BOLOS' one #416

yogh333 opened this issue Aug 10, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@yogh333
Copy link
Contributor

yogh333 commented Aug 10, 2023

os_lib_call()does not throw exception as on device: in case the called application is missing, it makes the main app crashes with no way to handle the exception (as it is the case on device). For consistency reason, its behaviour shall be aligned with target.
@yogh333 yogh333 changed the title os_lib_call implementation is different from BOLOS one os_lib_call implementation is different from BOLOS' one Aug 10, 2023
@yogh333 yogh333 added the bug Something isn't working label Aug 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@yogh333