[英]Browser ContentObserver not being called even using different URI's
[英]Sync Adapter called twice using ContentObserver
因此,我一直遇到這樣的問題:在我顯式調用requestSync時首先調用onPerformSync,然后在30或60秒(但主要是60秒)之后調用它,這很奇怪。 我正在使用ContentObserver,並且僅當我使用ContentObserver時才會發生此行為。 我嘗試直接從我的內容提供者調用requestSync,並且沒有觸發其他onPerformSync。 我的代碼摘錄如下。
提供者調用notifyChange
@Nullable
@Override
public Uri insert(@NonNull Uri uri, ContentValues values) {
Log.d(LOG_TAG, "Inserting with uri " + uri + " with values " + values.toString());
SQLiteDatabase db = mOpenHelper.getWritableDatabase();
int match = sUriMatcher.match(uri);
....
// This direct requestSync call does not trigger extra syncs
//Bundle extras = new Bundle();
//extras.putString(SyncAdapter.CHANGED_URI, uri.toString());
//getContext().getContentResolver().requestSync(SyncAccount.getAccount(), Contract.CONTENT_AUTHORITY, extras);
getContext().getContentResolver().notifyChange(contentUri, null);
return contentUri;
}
具有onChange的ContentObserver
public class TableObserver extends ContentObserver {
private final static String LOG_TAG = TableObserver.class.getSimpleName();
private final Account mAccount;
public TableObserver(Handler handler, Account account) {
super(handler);
mAccount = account;
}
@Override
public void onChange(boolean selfChange) {
super.onChange(selfChange, null);
}
@Override
public void onChange(boolean selfChange, Uri uri) {
Log.d(LOG_TAG, "Provider changed here: " + uri.toString());
Bundle args = new Bundle();
args.putString(SyncAdapter.CHANGED_URI, uri.toString());
ContentResolver.requestSync(mAccount, Contract.CONTENT_AUTHORITY, args);
}
}
帶有onPerformSync的同步適配器
public class SyncAdapter extends AbstractThreadedSyncAdapter {
private static final String LOG_TAG = SyncAdapter.class.getSimpleName();
public static final String CHANGED_URI = "changed_uri";
private ContentResolver mContentResolver;
public SyncAdapter(Context context, boolean autoInitialize) {
super(context, autoInitialize);
mContentResolver = context.getContentResolver();
}
public SyncAdapter(Context context, boolean autoInitialize, boolean allowParallelSyncs) {
super(context, autoInitialize, allowParallelSyncs);
mContentResolver = context.getContentResolver();
}
// This is automatically performed in a background thread.
@Override
public void onPerformSync(Account account, Bundle extras, String authority, ContentProviderClient provider, SyncResult syncResult) {
Log.d(LOG_TAG, "Synchronizing: " + extras.get(CHANGED_URI));
}
}
通過將false傳遞給notifyChange來修復它,該方法確實刪除了該方法與網絡行為的同步,如下所示:
getContext().getContentResolver().notifyChange(contentUri, null, false);
聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.