Sorry, I should have also made it clear that more things do not throw permissions exceptions. Moving up to 1.0 I have noticed a lot of things that simply fail and when trying to catch the exceptions nothing is being thrown. These problems were all solved by uses- permissions nodes in the Manifest, but I think if a program doesn't have the proper permissions to do something it should be made clearer rather than just closing, or am I missing something?
On Jan 23, 5:39 pm, MaxImUmZ <[email protected]> wrote: > I have a program that fails to start. When I remove this line of code > from the startup it starts with out error... > db = SQLiteDatabase.openOrCreateDatabase(data, cf); > > data is a file that has been made, I have tried multiple locations > none worked. cf is a cursorfactory. This worked perfectly before > version 1.0 and also when put in a try/catch statement still errors > out. It is the process has stopped unexpectedly error. Any thoughts > as to what permissions I could give the app to make this work? Am I > heading in the wrong direction? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
