ala https://github.com/joinspontaneous/react-native-loading-spinner-overlay

see https://medium.com/@kswanie21/react-native-deployment-to-iphone-76d8254f1505

and document how to do this

There have been updates to the storybook monorepo:

• • The devDependency @storybook/react-native was updated from 5.2.2 to 5.2.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the storybook group definition.

storybook is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Various bits of the app refer to org.reactjs.native.example and I need to work out how to remove that. My first attempt at doing so wound up with the app breaking, so it's not as easy as just deleting it.

Ref https://stackoverflow.com/questions/36119754/how-to-change-the-bundle-identifier-within-react-native (though take all the advice in there with several grains of salt)

The dependency react-redux was updated from 7.1.1 to 7.1.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

react-redux is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

• make this a public repo
• add ci configuration and badges.
• add codecov.io configuration and badges
• add greenkeeper.io config and badge

The devDependency eslint-plugin-jsx-a11y was updated from 6.2.1 to 6.2.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-jsx-a11y is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

maybe a generic errors popup of some kind. have a think about this.

When the app first starts dispatch restoreKeys

There have been updates to the babel7 monorepo:

• • The devDependency @babel/core was updated from 7.5.5 to 7.6.0.

• The devDependency @babel/runtime was updated from 7.5.5 to 7.6.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

• Do not log the user in but instead remove Balances Tab if there

The dependency redux-saga was updated from 1.0.4 to 1.0.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

redux-saga is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The app needs a logo.

Apple

https://developer.apple.com/design/human-interface-guidelines/ios/icons-and-images/app-icon/

App Icon

Spotlight

Settings

Notifications

note iOS automatically adds a 1-pixel stroke to all icons so that they look good on the white background of Settings.

Android

See https://material.io/design/iconography/#specs (and see if you can make any sense of that)

• read the blog entry about rn 0.60.0
• read react-native-open-source-update
• check the compatibility of all dependencies
• unlink all dependencies react-native unlink
• run rn-update-deprecated-modules
• install react-native-clean-project
• run react-native clean-project-auto
• run react-native upgrade
• go through the upgrade helper and check for issues
• test it: run yarn test
• deploy to simulator
• deploy to phone

• showSplash screen briefly and preload keys, and if keys are present then pre-load balances
• rename Login to Settings
• if no keys then navigate directly to the Settings screen
• hide Balances screen from navigation if there are no keys entered
• add icons to navigation
• remove Splash from navigation
• add a "clear keys" button to Settings
• fix the screen headers

add the ir-api and update the saga and actions

add more detail here

The dependency react-redux was updated from 7.1.0 to 7.1.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

react-redux is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency prettier was updated from 1.18.2 to 1.19.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

There have been updates to the storybook monorepo:

• • The devDependency @storybook/react-native was updated from 5.3.13 to 5.3.14.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the storybook group definition.

storybook is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

rn-nodeify installed a bunch of out of date dependencies. Work out how to update them

The user has the option to require auth before the app has access to their keys

In which case ensure the user has given their auth, via faceId, touchId or PIN code before loading the api keys from the device's keychain.

see https://medium.com/react-native-training/integrate-touch-id-and-face-id-to-your-react-native-app-707e7db17edc for how to do this

see also issue #5

The table is very static. It would be better to have it with a fixed header, then a scrollable middle, and a fixed footer.

There have been updates to the babel7 monorepo:

• • The devDependency @babel/core was updated from 7.5.5 to 7.6.0.

• The devDependency @babel/runtime was updated from 7.5.5 to 7.6.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

set the prop secureTextEntry to true (see https://facebook.github.io/react-native/docs/textinput#securetextentry)

The user needs to provide their apiKey and apiSecret

Create a form with fields:

• apiKey
• apiSecret

dispatch saveKeys on submit.

Display a table with the following data

with numbers aligned on the .

replace the Login screen with a Balances screen

• if there are no keys then show a button to navigate to the Login screen
• if there are keys but no balances then dispatch getBalances when the page loads
• if there are balances then show AccountBalances screen with a refresh button

The layout and overall design need some love.

• make all type responsive to screen size, pixel density, screen orientation, and user-preferences (for example if the accessibility settings have been used to scale the fonts for a device, the layout needs to adjust)
• improve the table layout
• make the buttons less huge
• make the screen headers work properly

see https://github.com/oblador/react-native-keychain