-
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
Add device syncing Ability #6
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ly seems to work for android)
…rors so I had to refactor / update the podfile
…ues - will work to reinstate later
…ass.ios' because the developer web pages was rejecting the former. I have started to inquire with apple as to why this is so this might get changed back at some point if it can be resolved
…sed on dart formatting
… to not cause errors (specifically on iOS)
… it required so it works
…red by darts formatting rules
… darts formatting rules
…erred by darts formatting rules
…rrance of darts formatting rules
…rance of darts formatting rules
…e is defined as a string
…e of darts formatting rules
… preferred by darts formatting rules
…rred by darts formatting rules
…he filename. make a notification class for handling notification objects in a more standard way
… and sends responses to the scanning device
…is point the public 'ability' to alter the audit log is not available (but that could change in the future)
… sets to ensure there is no accidental redundency when adding multiple pointers to objects like the vaults or device syncs
…changes to Secrets, changes to vaults, changes to devices and device syncs, and any export or import of data
…ormatted so it can be legible to go through the timeline
…key setup, notification manager setup, shared preferences setup, and the default vault setup
…hey want to see notifications for actions taken on secrets that were shared with the 'Readonly' or 'Manage' access - this notification could trigger often (even for simply clicking on a secret in the list view so options may need to be able to be more fine grained at somepoint)
…set to 'Default Password Generation' which is just a duplicate
…e and use the preference value to determine the size to display the preview
…t launch cpmmand to ensure that when not launching a url in the app the system browser is used
…s as well (not just the radio buttons)
… line up on the end of the line
…ced - because it takes time to actually fetch the id and it can get cleared out of memory at any point store it in a shared preferences and populate the preferences by registering a callback for when subscription status changes
…d-Only' can be displayed properly and consistantly
* create a new `normal_backgound.xml` to differentiate between the normal background and the launch splash screen background * setup base android manifest changes needed for supporting android embeddings * the Main activity to maintain support for the Secure Flags in android and turning on android embedding 2 * the dependency libraries to support new android 2 embedding * the pubspec app description * clean up the pubspec file and remove unnecessary comments * use a mono spaced font that will make it easier to differentiate character that are similar (liLI1 | 0oO | etc.) * the barcode scanner library update had a breaking change which required updates to the app to function appropriately * the nullpass "null" symbol which is used throughout the app * the assets to the pubspec file * add mew library for adding screen security to the app without requiring changes to the native code itself * remove no longer necessary native code that was used for hiding the screen when it moves to the background (like when going to the app switcher) * bump the minimum SDK version for android to get rid of the multi dex build issues * bump the Podfile lock and pubspec.lock specifically for OneSignal related versioning and building issues * commit auto updated project.pbxproj shellscript * add remaining of auto updated project.pbxproj configuration changes to the app.framework and flutter.framework references as well as the profile, debug and release build configs * migrate to the newer Podfile format in an attempt to minimize build errors for iOS * update the ios project config based on the new Podfile changes * update the lock file based on the new Podfile - note vibration has been added but may cause issues on ios simulator * add missing vibration dependency references to the project configuration * re-add references to vibration library * ensure this doesn't get accidentally published as a library * add the update pubspec lock including updated dependencies and updated dart version env requirements
…ted `ios/Flutter/Flutter.podspec` file that should not have been checked into version control
…conflicts for PR #6
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On key feature that I want in the app is the ability to back and share passwords onto another device. This is an integral feature because we don't have any backend servers so we don't have the ability to store or back anything up ourselves, therefore users should be able to back this up onto other devices like an old phone, a loved ones phone, or even a simulator on a computer (i don't believe iOS simulators work because of APN limitations and simulators are not necessarily always on so some data may not be sync'd properly).
some other areas this diff doesn't address that will need to be addressed in a later commit is recovering data from a "backed-up" device.