Samsung Legacy 2014 TV not updating application - samsung-smart-tv

I have followed the steps given in http://developer.samsung.com/tv/develop/legacy-platform-library/art00121/index, and the application appears on the Smart Hub on the TV. However, when I make some changes in the application, and package it again selecting "Update the packaged files on the server", do a "Apps Sync" and run the application, the updates are not reflected.
I have tried changing the application name and version in config.xml. Only the application name changes in smart hub, but the application when opened is what was installed the first time on the TV.
If a new project is made and the same steps are followed, the new application appears on the smart hub, but an update to it has the same problem.
Am I missing something while packaging the same application for a second time?

Not sure if this is useful but I believe the device seems to cache the files. I had the same issue today and was quite frustrating.
I managed to find two solutions:
1) shut down the device and re-launch again (connect to server and the Apps Sync)
2) when you export the app in the IDE, make sure you name the package name differently + title & description need to be different too.
By doing this, Apps Sync will add another app (so you'll have two of the same app, but just click on the last one that appears in the apps list - hope that makes sense). If you want to remove the apps, simply access the widgetlist.xml which will be in the root of your server and then remove the apps references from there.
I hope that helps.

Related

Why would my side-loaded Windows Store app go no further than the splash screen?

I have a Windows Store App that, of course, runs fine on my dev machine.
After creating the package to side load for testing, I installed it on another (desktop) machine. Using the instructions for side-loading contained on pages 25 and 26 of Brundritt's free ebook "Location Intelligence for Windows Store Apps", my app seems to install just fine, except that the app is not added to the Windows 8.1 start screen at the end, as expected.
Nevertheless, I can find the app via the Search functionality - I type the name, it shows up in the "found" list (with its logo), but when I try to run it, the splash screen simply "flashes" and then the app disappears. It icon is indeed parked on the taskbar, and every time I click it, the splash screen flashes, but that's all.
This is a Windows 8.1 app that contains a Bing Map, SQLite (and sqlite-net), as well as ExifLib.
It does show up in Task Manager's "App History" tab.
How can I rectify this problem, or at least determine what the problem might be?
UPDATE
This may (or may not be) significant: the version of the app I sideloaded was built in debug mode. Do I need to build in release mode for this to work?
Also: After building in release mode (for the first time) on the dev machine, it no longer finds the SQLite data that had formerly existed. Does changing from debug to release change the path to the database or something?
Does this help? http://blogs.msdn.com/b/vcblog/archive/2012/09/28/10354327.aspx It appears that the app needs to be built in release mode to work properly.

How do you remove an app from iPhone Configuration Utility?

I'm attempting to install an archive build of my app using iPhone Configuration Utility but am unable to.
The app appears in the Applications section, however when I click on the Devices section, then choose the Applications tab it isn't listed there.
I think this might be because I changed the app name and the app with the old name is still listed in iPhone Configuration Utility and as they have the same app id it may be getting confused.
However there seems to be no way to delete the old app from within iPhone Configuration Utility to see if this clears the problem.
In iPhone Configuration Utility, under Library->Applications, select the application and click Edit->Delete.

iOS Enterprise distribution through webapp?

We need to be able to easily install our in-house apps on our devices and quickly update them no matter where they are.
I'm looking into different ways of distributing our in-house app to our staff. So far I've found iTunes, iPhone Configuration Utility, install via a web link, etc...
Our devices will more than likely not be in proximity to our office and mostly rely on 3G, so it seems that the web link is my best free option.
I made a web-app that I can add to the home screen to install / update the application. What I want to do is make the web-app more intelligent: Display an "Install" button or an "Update" button. Ideally I want the web-app to know what version of the app is already installed.
The only way I can think of doing this: When the user clicks the install link store the version number in localStorage. When they return later compare that to what's available and display the right button.
The biggest issue with this "solution" is, what if the user clears Safari's cache? Do home screen apps have their own protected cache?
Another option is have the app itself relay its version number to the server and store that in a database. But this is more complicated, so I would like to avoid that. If I could use a url scheme to get the version number without launching the app, that would be acceptable. But I don't think it's possible.
So given that we need to readily update the app quickly on the device no matter where our staff travel, what is the easiest, best, and preferably free solution?
It's really simple... the app can update itself by opening a weblink... you don't have to open it in safari. So on app start just check the version from the web server and when it's not up to date it can update itself.
You could also send a remote notification if it's urgent.

Check whether app updates work without submitting to App Store

I have an application already on the store and would like to release an update. Since my app deals with databases and I've had to change some parts of it, I would like to ensure that the update does not affect the existing functionality in any way once the user updates from the App Store.
What I did was this - install the first version of my app on my device. Changed the update's version in info.plist to 1.1 and run it via xcode (and install on my device). But what happens by doing this is some of the changes I made to the XIBs do not show up. It looks as if the app was only half-updated (if you know what I mean)
Is there any way to update an existing app programmatically without having to go through the app store and then find out it could lead to a disaster?!
Thanks for any help!
I would double check your build configuration. Between building the two versions of the app, I would recommend a "Clean All" just to be safe. The process you described works to verify updates. The only other alternative I can come up with is to create Ad-hoc distributions of both versions of your app, and install those.

creating a free version of an app, but having the app separate on debug device

I was just making a free version of one of my apps. I copied the folder, renamed the project, and changed the icon file, loading screen, interface, and code. BUT YET it still replaces a build on my phone.
1)how do I stop this from happening (i want both the free and paid version on my phone)
2) if you can fix this, will a customer who has the paid, and downloads the free, will that replace it on their phone?
I really need to know these, as I have the app ready to go, and would like to get it before the end of the week.
cheers
Sam
You need to have a different app bundle identifier. I think that's your problem.
Long answer:
Go into your projectname-info.plist file and change the CFBundleIdentifier.
I'd recommend something like:
com.mycompany.mycoolapp for the app store
com.mycompany.mycoolapp-beta for the beta version
You should actually be able to set up the "Debug" build configuration to use a different info.plist file configured with a different CFBundleIdentifier and a different icon filename. That way you'll automaticlly get the beta ID and icon, etc for the Debug build and the real id/icon for the full one.
This should allow users to install and use both the production and test versions of the apps at the same time without confusion.
You might also find this IPA target template helpful if you're doing ad-hoc distribution to Windows users for testing:
http://devblog.appmagination.com/2010/01/target-template-for-building-iphone-ipa.html