2017-10-23 24 views
1

私はしかし、成功もしなくても...レルム非同期タスク

を参照してください、デバッグしようとした...

をいくつかのオブジェクトを挿入するためのAsyncTransactionを使用しようとしているが、一瞬のためにそれが失敗しました私のコード:私はデバッグするとき、私は非同期トランザクションのいずれかのコールバックに行かなかったことがわかり

realm.executeTransactionAsync(
       new Realm.Transaction() { 
        @Override 
        public void execute(@NonNull Realm realm) { 
         Log.i("Insert", "Insert start"); 
         realm.insert(character); 
        } 
       }, new Realm.Transaction.OnSuccess() { 
        @Override 
        public void onSuccess() { 
         Log.i("Insert", "Insert complete"); 
         finish(); 
        } 
       }, new Realm.Transaction.OnError() { 
        @Override 
        public void onError(Throwable error) { 
         Log.i("Insert","Error " + error.getMessage()); 
        } 
       }); 

、ログが存在しない、私を助けることができるものは何もありません。事前に

感謝、

EDIT:

public RealmAsyncTask executeTransactionAsync(final Transaction transaction, 
     @Nullable final Realm.Transaction.OnSuccess onSuccess, 
     @Nullable final Realm.Transaction.OnError onError) { 
    checkIfValid(); 

    //noinspection ConstantConditions 
    if (transaction == null) { 
     throw new IllegalArgumentException("Transaction should not be null"); 
    } 

    // Avoid to call canDeliverNotification() in bg thread. 
    final boolean canDeliverNotification = sharedRealm.capabilities.canDeliverNotification(); 

    // If the user provided a Callback then we have to make sure the current Realm has an events looper to deliver 
    // the results. 
    if ((onSuccess != null || onError != null)) { 
     sharedRealm.capabilities.checkCanDeliverNotification("Callback cannot be delivered on current thread."); 
    } 

    // We need to use the same configuration to open a background SharedRealm (i.e Realm) 
    // to perform the transaction 
    final RealmConfiguration realmConfiguration = getConfiguration(); 
    // We need to deliver the callback even if the Realm is closed. So acquire a reference to the notifier here. 
    final RealmNotifier realmNotifier = sharedRealm.realmNotifier; 

    final Future<?> pendingTransaction = asyncTaskExecutor.submitTransaction(new Runnable() { 
     @Override 
     public void run() { 
      if (Thread.currentThread().isInterrupted()) { 
       return; 
      } 

      SharedRealm.VersionID versionID = null; 
      Throwable exception = null; 

      final Realm bgRealm = Realm.getInstance(realmConfiguration); 
      bgRealm.beginTransaction(); 

    // NOTHING IS DONE AFTER IS POINT ..... 
      try { 
       transaction.execute(bgRealm); 

       if (Thread.currentThread().isInterrupted()) { 
        return; 
       } 

       bgRealm.commitTransaction(); 
       // The bgRealm needs to be closed before post event to caller's handler to avoid concurrency 
       // problem. This is currently guaranteed by posting callbacks later below. 
       versionID = bgRealm.sharedRealm.getVersionID(); 
      } catch (final Throwable e) { 
       exception = e; 
      } finally { 
       try { 
        if (bgRealm.isInTransaction()) { 
         bgRealm.cancelTransaction(); 
        } 
       } finally { 
        bgRealm.close(); 
       } 
      } 

      final Throwable backgroundException = exception; 
      final SharedRealm.VersionID backgroundVersionID = versionID; 
      // Cannot be interrupted anymore. 
      if (canDeliverNotification) { 
       if (backgroundVersionID != null && onSuccess != null) { 
        realmNotifier.post(new Runnable() { 
         @Override 
         public void run() { 
          if (isClosed()) { 
           // The caller Realm is closed. Just call the onSuccess. Since the new created Realm 
           // cannot be behind the background one. 
           onSuccess.onSuccess(); 
           return; 
          } 

          if (sharedRealm.getVersionID().compareTo(backgroundVersionID) < 0) { 
           sharedRealm.realmNotifier.addTransactionCallback(new Runnable() { 
            @Override 
            public void run() { 
             onSuccess.onSuccess(); 
            } 
           }); 
          } else { 
           onSuccess.onSuccess(); 
          } 
         } 
        }); 
       } else if (backgroundException != null) { 
        realmNotifier.post(new Runnable() { 
         @Override 
         public void run() { 
          if (onError != null) { 
           onError.onError(backgroundException); 
          } else { 
           throw new RealmException("Async transaction failed", backgroundException); 
          } 
         } 
        }); 
       } 
      } else { 
       if (backgroundException != null) { 
        // FIXME: ThreadPoolExecutor will never throw the exception in the background. 
        // We need a redesign of the async transaction API. 
        // Throw in the worker thread since the caller thread cannot get notifications. 
        throw new RealmException("Async transaction failed", backgroundException); 
       } 
      } 

     } 
    }); 

    return new RealmAsyncTaskImpl(pendingTransaction, asyncTaskExecutor); 
} 
+0

Realmインスタンスをどこかに閉じていますか? –

+0

Unfortunatlyいいえ、私は私の答えを編集する、私は何もない場所を追加します – kevingiroux

+1

beginTransaction()スレッド間でブロックされている、他のスレッドでコミットされていないトランザクションはありますか? – EpicPandaForce

答えて

1

私はトリックを発見しました。エラー

(非書き込みトランザクションに書き込めませんすることはできません)

第二の点を作成し、私のコンストラクタで

、私は別のいくつかのRealmObjectを追加するに、私は(のbeginTransactionを使用しました)親に、それasynctransaction

私はFIRSTPARTにRealmRecyclerViewを使用するための私のコードを変更するための他の部分にブロックし、私はもう

おかげ

問題を持っていませんでした