I have an application on iTunes which I think I mentioned to you previously. iSecure.
[url removed, login to view]
A user has commented they cannot transfer data from one phone to another. This I think is the case and an oversight in the design.
The app when installed retrieves the IMEI number and uses that along with another piece id data as the Key for the data encryption.
The database can be Exported via Email so the user can open an email to access the database.
Now if the data is moved to another phone, of course the IMEI number is different so the data is unrecognizable.
I think what I need is a Class and Form that asks the user for the original IMEI number and Code. This then pulls in the database, decrypts that, end encrypts it using the current IMEI number.
Depending on how the database data is encrypted and if it is messy then to write a class to decrypt the records, the easier option could be this...
- Create a new field called InitIMEI
- if this field is empty, as in the primary install on a phone, the app just does what it currently does for encrypting etc.
- if this field contains an IMEI, then the app uses this IMEI as the Key data
this would be the case if the user has done a transfer to a new phone and entered the primary phones IMEI for the data transfer.
Using this method (which is cheating and a short cut) if the user transfers phones 3 or 4 times, he would always need to enter the initial primary IMEI code from the first" phone that had the app installed on it. I'm ok with this approach as it is a quick and simple fix without the need to do much coding and then app testing.
Your thoughts ?