Databases
StackOverflow2013
Postsdbo
POAdding a calendar with ACCOUNT_TYPE_LOCAL to Android 4 makes its calendar crash
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAdding a calendar with ACCOUNT_TYPE_LOCAL to Android 4 makes its calendar crash
    primarykey
    data
    text
    <p>I want to add a new calendar to Android that does not get synchronized. I have written an App that does this using the new CalendarContract API from API level 14. The following code works fine. I can see the new calendar in Android's calendar app and add events to it.</p> <p>The problem is that the Android calendar app crashes when I select: Menu -> Calendars to display -> Calendars to sync</p> <p>Is there something wrong in my code or is it a bug in Android calendar?</p> <p>Mind that I do not want to actually use a sync adapter. The documentation of CalendarContract.Calendars says that this is not needed: "If a local calendar is required an app can do so by inserting as a sync adapter and using an ACCOUNT_TYPE of ACCOUNT_TYPE_LOCAL." I understand that "inserting as a sync adapter" means to append (CalendarContract.CALLER_IS_SYNCADAPTER, "true") to the URI.</p> <pre><code>public class CalendarMapper { private static final String ACCOUNT_NAME = "private"; private static final String INT_NAME_PREFIX = "priv"; private static Uri buildCalUri() { return CalendarContract.Calendars.CONTENT_URI .buildUpon() .appendQueryParameter(CalendarContract.CALLER_IS_SYNCADAPTER, "true") .appendQueryParameter(Calendars.ACCOUNT_NAME, ACCOUNT_NAME) .appendQueryParameter(Calendars.ACCOUNT_TYPE, CalendarContract.ACCOUNT_TYPE_LOCAL) .build(); } private static ContentValues buildContentValues(Calendar calendar) { String dispName = calendar.getName(); //Calendar.getName() returns a String String intName = INT_NAME_PREFIX + dispName; final ContentValues cv = new ContentValues(); cv.put(Calendars.ACCOUNT_NAME, ACCOUNT_NAME); cv.put(Calendars.ACCOUNT_TYPE, CalendarContract.ACCOUNT_TYPE_LOCAL); cv.put(Calendars.NAME, intName); cv.put(Calendars.CALENDAR_DISPLAY_NAME, dispName); cv.put(Calendars.CALENDAR_COLOR, calendar.getColor()); //Calendar.getColor() returns int cv.put(Calendars.CALENDAR_ACCESS_LEVEL, Calendars.CAL_ACCESS_OWNER); cv.put(Calendars.OWNER_ACCOUNT, ACCOUNT_NAME); cv.put(Calendars.VISIBLE, 1); cv.put(Calendars.SYNC_EVENTS, 1); return cv; } public static void addCalendar(Calendar calendar, ContentResolver cr) { if (calendar == null) throw new IllegalArgumentException(); final ContentValues cv = buildContentValues(calendar); Uri calUri = buildCalUri(); cr.insert(calUri, cv); } } </code></pre> <p>Here is the Stack Trace of the Exception that causes the calendar app to crash:</p> <pre><code> 03-22 07:12:39.437: E/AndroidRuntime(9730): FATAL EXCEPTION: main 03-22 07:12:39.437: E/AndroidRuntime(9730): java.lang.NullPointerException 03-22 07:12:39.437: E/AndroidRuntime(9730): at com.android.calendar.selectcalendars.SelectSyncedCalendarsMultiAccountAdapter.bindGroupView(SelectSyncedCalendarsMultiAccountAdapter.java:324) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.widget.CursorTreeAdapter.getGroupView(CursorTreeAdapter.java:207) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.widget.ExpandableListConnector.getView(ExpandableListConnector.java:445) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.widget.AbsListView.obtainView(AbsListView.java:2033) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.widget.ListView.makeAndAddView(ListView.java:1772) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.widget.ListView.fillDown(ListView.java:672) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.widget.ListView.fillFromTop(ListView.java:732) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.widget.ListView.layoutChildren(ListView.java:1611) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.widget.AbsListView.onLayout(AbsListView.java:1863) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.view.View.layout(View.java:11278) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.view.ViewGroup.layout(ViewGroup.java:4224) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1628) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1486) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.widget.LinearLayout.onLayout(LinearLayout.java:1399) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.view.View.layout(View.java:11278) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.view.ViewGroup.layout(ViewGroup.java:4224) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.widget.FrameLayout.onLayout(FrameLayout.java:431) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.view.View.layout(View.java:11278) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.view.ViewGroup.layout(ViewGroup.java:4224) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1628) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1486) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.widget.LinearLayout.onLayout(LinearLayout.java:1399) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.view.View.layout(View.java:11278) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.view.ViewGroup.layout(ViewGroup.java:4224) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.widget.FrameLayout.onLayout(FrameLayout.java:431) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.view.View.layout(View.java:11278) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.view.ViewGroup.layout(ViewGroup.java:4224) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1489) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.view.ViewRootImpl.handleMessage(ViewRootImpl.java:2442) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.os.Handler.dispatchMessage(Handler.java:99) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.os.Looper.loop(Looper.java:137) 03-22 07:12:39.437: E/AndroidRuntime(9730): at android.app.ActivityThread.main(ActivityThread.java:4424) 03-22 07:12:39.437: E/AndroidRuntime(9730): at java.lang.reflect.Method.invokeNative(Native Method) 03-22 07:12:39.437: E/AndroidRuntime(9730): at java.lang.reflect.Method.invoke(Method.java:511) 03-22 07:12:39.437: E/AndroidRuntime(9730): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784) 03-22 07:12:39.437: E/AndroidRuntime(9730): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551) 03-22 07:12:39.437: E/AndroidRuntime(9730): at dalvik.system.NativeStart.main(Native Method) </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USharsel
    1. USharsel
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAdding a calendar with ACCOUNT_TYPE_LOCAL to Android 4 makes its calendar crash
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POAdding a calendar with ACCOUNT_TYPE_LOCAL to Android 4 makes its calendar crash
      1. USuser1412035
      1. VTFavorite
    3. VO
      singulars
      1. POAdding a calendar with ACCOUNT_TYPE_LOCAL to Android 4 makes its calendar crash
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload