Blackberry Webworks delete webstorage - blackberry-webworks

How can i delete webstorage data?
I am using HTML5 db to store app Data for my webworks blackberry app. The problem is when i delete the app the app data is still there. If i install the app again the old data is still there.

You can delete the database manually via the "File" explorer. I found my created database in /Device/BlackBerry/system/appdata/rim/webstorage/(application name). Or you can simply upgrade your database version so that the newer one will be used instead of the old one.

Related

Why does Trigger.IO app need to be uninstalled when upgrading on iOS?

I'm testing a Trigger.IO app built with Forge v1.4 on an iPod running iOS 6. I've been installing the .ipa through a distribution provision profile.
Occasionally, after installing an updated version, the app would launch but not run correctly. I traced this behaviour to the window.forge being absent, presumably due to a bad initialization. I would then make sure to kill the app process before installing updates and my recollection is that this seemed to make the problem go away.
Now, I've added the Facebook and Splash modules and my app now consistently won't go past the splash screen after I install an upgraded version unless I forcibly uninstall the old version first. Presumably, it dies before creating the webview. Any idea why I would need to uninstall my app first before upgrading? Is this a known behaviour?
I want to make sure that my users don't experience this when upgrading.
My app runs happily without Forge, and doesn't have any particular dependencies on localStorage data. I don't have a Mac and have been installing via iTunes in Windows, so I don't think I can access logging information.
You should have a look at this post:
How application get update from apple store?
The quick answer is when you update an app, you install the new bundle but you keep the user data stored previously such as a local DB. If you changed the local DB in the new app (or anything else) your app can crash when updated but is fine when downloaded from scratch.

Database path not been used by application - Logic issue

I have created a sqlite database. and dragged it on to my projects resource folder.
In my project i am accessing a sqlite file from
/Users/user12/Library/Application Support/iPhone Simulator/4.3.2/Applications/1F219005-A4ED-4794-81FC-65EEF8D243EF/Documents/db.sqlite
I am not using the sqlite file that was added to the project. and my project is accessing the DB file from the above location.
So, now when i try to launch my application from a different mac i am unable to launch the application because the DB is not found in that path. So how could i solve this ?
note: i used FMDB.
My final objective is to give this application to my client and since he will be running the app on his iPhone, he should be able to access the sqlite file with no issue. So what changes should i make ?
Surely xcode in other machine will have a different path. Try to place the sqlite file at the app path created by xcode on the new machine.
EDIT:
To do what you've said in your comment i suggest to create an ad-hoc certificate. Then use xcode to create your archive.
But the path of your sqlite file should be in your main bundle.
ps: You need the UDIDs of your client iPhones to add the devices to the portal.

Is it possible to get information out of install plist?

I'm trying to find out if it's possible to get any information out of the plist used to install an enterprise app onto a device to then store for the app to use.
What I'm trying to do is pass some information to an app on install so that it can then use that information within the app. I can't make this data static, so it can't be stored in the Info.plist file in the root; it needs to be dynamic and will change on an install by install basis. I also can't pass the information by a web service etc, it needs to happen on install.
Many thanks,
Davoc
Since you're distributing for enterprise (ie not through the App Store), here's a thought: since you can re-codesign an app package after it has been built, and an ipa is simply a renamed zip, why don't you put the app on the server as an unzipped package, and have a server side script insert the settings.plist, zip and codesign the app every time someone downloads the app?
In Summary:
1. Compile the package, but don't code-sign it.
2. Place the app folder (*.app) onto a server.
3. When the user downloads it by requesting a link, have the server generate your desired url into a plist and overwrite the existing settings.plist in the bundle
4. Code-sign the package using apple's codesign tool via command line
5. Zip the whole thing and rename to .ipa
6. Serve the package to the client.

How to test an iPhone application update?

I already have an iPhone application (version 1.0) available in the App Store and am ready to submit a newer version (version 1.1). How do I test the new upgrade to make sure that the current sqlite database and property list files on the earlier version do not get deleted/overwritten etc? The new version assumes the old data in both the sqlite database and property lists remain.
Or better yet, is there a resource I can use to walk me through what to watch for when developing an application update?
The way we tackled this when we wanted to test our database upgrade code was to use ad hoc distribution.
We had our testers download the 1.0 app from iTunes and install it on their test devices.
Then we built an Ad Hoc distribution of the app using a configuration based on the Release config, and made sure that it had the same bundle identifier. As long as the bundle identifier is the same, the new app should overwrite the previous version.
We asked our testers to install the ad hoc build as they normally would, by dragging it into itunes and then syncing the device to simulate upgrading.
As far as I know, this is identical to the user downloading and installing an upgrade via the app store on the device itself.
As you'd expect, the documents folder should be left intact, leaving your database in place, and your app should be able to run its upgrade code to modify the database in the way you need.
Hope this helps :)
Test like so:
delete app from device.
install v1.0 app (or .ipa file) into iTunes
sync to device, iTunes will install the app
launch app on device, create and save data, etc.
quit app on device
install v1.1 app (or .ipa file) into iTunes; iTunes will ask to confirm replacing older version of the app.
sync to device, iTunes will update the app
launch app on device
test using existing data with new version of the app.

iPhone app doesn't stay installed (icon disappears)

I'm trying to install Zxing on my iphone from source (I know I can get it at the app store, but I want to modify some things in it).
The problem I'm having is that the app won't stay installed on the phone. It will run without a problem, but no icon will appear after I quit the app. I thought it had to do with my manually editing the codesign information in the project.pbxproj but after the developers changed the codesign identity they had left in the checked in version, the problem still persists.
I tried deploying an app I had developed from scratch and that worked fine.
I'm new to this, so any help would be much appreciated. You can download the zxing code from here:
svn checkout http://zxing.googlecode.com/svn/trunk/ zxing-read-only
Have you downloaded a copy from the App Store? I had one app (built from Xcode) that wasn't staying around after a sync and I found it was because iTunes was looking at my application syncing preferences and it wasn't selected to sync (as I had the Xcode build version on there, I didn't want to sync that version). However, it presumably removes the built app because I said I didn't want to sync any version of it.
Checking the checkbox to sync the app in iTunes kept the Xcode built version on there without installing the App Store version.
Hope this helps.
I think the problem had to do with my iPhone firmware. It might be a bug from Apple as I got an email from truphone saying that users were experiencing similar problems. I re-installed firmware, and could install it fine, and sync other apps. As soon as I did a restore from a previous backup, it broke again... what a pain. Case closed.