-
Notifications
You must be signed in to change notification settings - Fork 0
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
[WASH-931] Add share method to iOS plugin #15
Conversation
example/lib/main.dart
Outdated
developer.log("example flow succeeded"); | ||
} catch (e) { | ||
developer.log("example flow failed becaused $e"); | ||
} |
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.
There was a missing brace here causing variable declaration errors that I inadvertently fixed in writing onWriteThenShareRecordButtonPress
.
I did not notice this until I started a new branch off of trunk
to start working on read record. Merging this will fix this, but at the moment trunk
is non-functional because of it. At a glance, error was introduced in commit 7c7cd2229845d256c8a6d5f5144ce65e1ca7eb55
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.
my bad ✋🏽
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.
When we can I would like to get clarity on where that cryptoError is being generated by the swift-sdk to verify that we are not going to be bitten later.
- Adds a share record method to iOS plugin - Adds a new test to example app that writes then shares a record
4cb3e96
to
db86b0d
Compare
shares a record
Using this draft to communicate current progress on sharing records.
share
is confirmed to successfully share a record by runningonWriteThenShareRecordButtonPress
test inmain.dart
then confirming in dashboard and docker logs.The
shareResult
value returned inshare
's callback returns acryptoError
object when sharing a new record type, which causes execution to fall into theFlutterError
case. I confirmed that this was not an issue with re-sharing the same record given that doing so returns the expected409
instead of acryptoError
.I will mark in in-line comments where the callback returns a
cryptoError
.