Android Question ConfigureHomeWidget - FileNotFoundException

[PhilipK]

Hi,

I have had an application running well for months, on my old HTC phone (Gingerbread). I have just upgraded my phone Sony Z1 (KitKat) and found the application to be unstable.

Using the debug tool traps an error when configuring the home widget:

    rv = ConfigureHomeWidget("hp", "rv", 30, "MainWindow")

Error in Debug Window:

I have checked that the file hp.bal exists in the files folder. Is it some sort of file access error? Very odd considering it worked for months before. Obviously a hardware and OS change...

Thanks.

 

[Pendrush]

Check
http://www.b4x.com/android/forum/threads/android-home-screen-widgets-tutorial-part-i.10166/#content
and
http://www.b4x.com/android/forum/threads/android-home-screen-widgets-tutorial-part-ii.10356/#content

 

[PhilipK]

Check
http://www.b4x.com/android/forum/threads/android-home-screen-widgets-tutorial-part-i.10166/#content
and
http://www.b4x.com/android/forum/threads/android-home-screen-widgets-tutorial-part-ii.10356/#content

Thanks Pendrush. I'll check the implementation. Still don't get why there's an exception when nothing code-wise has changed. Hopefully, it'll come clear...

 

[DonManfred]

Maybe you need to uninstall and install the app again.
Probably you have to use

#DebuggerForceStandardAssets: true
' and/or
#DebuggerForceFullDeployment: true

in the Project attributes if you are compiling in debug-modes.

You error suggest that the bal-file (layout) is missing.

 

[Erel]

It is not related to this specific error, however you need to test widgets in release mode.

Have you also added the file to the Files tab?

 

[PhilipK]

Thanks guys,

The BAL file has always been present and I just can't understand why there's a 'FileNotFound' exception.

Tried the '#DebuggerForceStandardAssets: True' and that got over the error (in debug mode). However, the debug installed widget didn't respond to touch. So I've abandoned Debug Mode.

Now compiled in release mode and it works. Thanks Erel.

Time to get back to the issue with the app.: tracking down the instability. Lack of response to touch inputs after hibernation, over time. I reckon it is something to do with the OS interfering with the service, in some way.

Thanks again.