SyncAdapter | Sync online database and SQLite database | Database library

You are constructing messageOberserver [sic] (messageObserver)

We tweaked your idea and came up with this (in Kotlin, see below for Java):

I have 3 methods to try and accomplish this, never tested them though:

Solution 1 - setSyncAutomatically:

The problem was in the authority string argument in ContentResolver.setSyncAutomatically(account, authority, true);, it needs to be "com.android.contacts" for contacts synchronization

A couple of things you need to do:

1. Implement a SyncService and declare it on AndroidManifest
2. create a contacts.xml file that will that the contact editor how to parse and edit contacts related to your account

See: https://github.com/xwiki-contrib/android-authenticator/blob/master/app/src/main/AndroidManifest.xml#L81-L94 https://github.com/xwiki-contrib/android-authenticator/blob/master/app/src/main/res/xml/syncadapter.xml https://github.com/xwiki-contrib/android-authenticator/blob/master/app/src/main/res/xml/contacts.xml

as examples.

I recently had a similar issue with Fortify. As Silvia Ragui pointed out Fortify doesn't analyze this runtime process correctly. While installIfNeeded() and installIfNeededAsync() will update the security provider in real world deployment of your APK, but it does not seem to clear the error when you resubmit to Fortify.

However the underlying issue is the out of date Security Provider which is usually due an out of date play services library in your package.

Here is the recommendation directly from fortify dashboard:

Android relies on the security Provider to provide secure network communications. The default device cryptographic libraries are typically older versions of OpenSSL that contain known flaws. To overcome this, Google provides a mechanism for an application to “patch” their local copy of OpenSSL via the Google Play Services ProviderInstaller client. It’s been determined that the app is not using the updated provider, leaving the application exposed to older known OpenSSL vulnerabilities and weaknesses.>

The actual problem is the same as the last line in Silvia's logs:

W/GooglePlayServicesUtil Google Play services out of date

In our case we updated to the latest version of Play Services in our package as well as implementing the fix above (when we did so we found there was small error that had to be fixed, and was probably preventing the update from patching the Security Provider)

The new build successfully cleared the issue. I suggest you update you to the latest Play Services as this will also update the Security Provider.

I found the problem. When I call accountManager.addAccount(..) or accountManager.removeAccount(..) or accountManager.setPassword, it cause to call syncAdapter.onPerformSync(..) at then sendRequest to server , ... . It causeses infinity loop. I solved the issue with adding extras to Bundle when calling ContentResolver

My first question is why you want to keep doing something even though the user has killed your application.

JobService, WorkManager, Firebase JobDispatcher act like Alarm Manager and will run periodically but with longer intervals (15 mins).

SyncAdapter Requires a service to run.

A Service appears to be your only option but the user can still kill it by going to settings and force closing your application and all of its services.

The fact that the function is running after the Service is detroyed is normal. You can't just stop a thread from outside (without knowing a lot about how the thread works). You could break the app, corrupt data, or cause a deadlock. So Android doesn't even try. Destroying the Service just changes some bookkeeping and prevents some things that require a Context from working, it doesn't stop any threads that are running.

Stopping after 120 seconds- sounds like the timer for background services. Did you call startForeground()?