Due to the migration of the _storeData() function from the scan screen to the validating screen (because the string should only be saved when the string is verified), code was copied to the validating class. It was not however, verified that a string actually got saved because the string stays in the memory of the app.
This pull request puts the qrString in the state within validating screen so the function can get accessed from other functions from the validating screen, like the wrapperFunction that calls _storeData().
Due to the migration of the _storeData() function from the scan screen to the validating screen (because the string should only be saved when the string is verified), code was copied to the validating class. It was not however, verified that a string actually got saved because the string stays in the memory of the app.
This pull request puts the qrString in the state within validating screen so the function can get accessed from other functions from the validating screen, like the wrapperFunction that calls _storeData().