ContentProvider InstantiationException

droozen · by **droozen** » Thu Mar 05, 2009 11:54 pm

So, I want to set a repeating alarm that will notify the user every day about something. So I make a repeating alarm that calls my BroadcastReceiver. The only thing my BroadcastReceiver does is start my service, because potentially (not likely, but potentially) it could take some time to do some work.

In my service I have:

Syntax: [ Download ] [ Hide ]

Using java Syntax Highlighting

 
       NotificationManager notifManager = (NotificationManager) getSystemService(Context.NOTIFICATION_SERVICE);
 
        Notification notif = new Notification(R.drawable.mydrawable, "Notification Text", System.currentTimeMillis());
 
        PendingIntent contentIntent = PendingIntent.getActivity(this, 0,
 
                new Intent(this, My.class), 0);
 
        ContentResolver resolver = getContentResolver();
 
        Cursor reminders = resolver.query(MyProvider.CONTENT_URI, 
 
                                                  null, null, null, null);
 
Parsed in 0.032 seconds,  using GeSHi 1.0.8.4

MyProvider is set up in the manifest as a Content provider, with the same authority as is represented by MyProvider.CONTENT_URI (the uri is context://<the authority>/<more path>)

However, my query method in my ContentProvider never gets called and I can't understand why...

droozen · by **droozen** » Fri Mar 06, 2009 2:44 pm

Upon further review, I realize that it was only "working" because the provider tag wasn't under the application tag. By "working", I mean, the reason why my application was running at all. When I put my provider tag under my application tag, like so:

Syntax: [ Download ] [ Hide ]

Using xml Syntax Highlighting

 
<application -- application data -->
 
        <provider android:name="--Fully qualified path to the class--" android:authorities="--authority--"></provider>
 
        ...
 
</application>
 
Parsed in 0.001 seconds,  using GeSHi 1.0.8.4

Now my application won't even start up because the provider won't instantiate.

MrSnowflake · by **MrSnowflake** » Fri Mar 06, 2009 3:54 pm

Did you look up the error?

droozen · by **droozen** » Fri Mar 06, 2009 5:04 pm

Sorry, yes. It's an InstantiationException with the class name as the message (or the authority as the message, I put it the same as the class name). No stack trace to provide. I've been trying to query ContentProvider with InstantiationException and getting no helpful results.

ContentProvider InstantiationException

ContentProvider InstantiationException

Who is online