Particle

I've tried with `core.clearProxyConfig()` along with the other methods, and on its own, the result is exactly the same, there is always one account when reading the account list after....

In case it might be helpful, currently this is my `SipManager` ````kotlin object SipManager { private const val TAG = "SipManager" @Volatile private var _factory: Factory? = null @Volatile private...

@Viish I've been trying to make this work without saving the account registration (passing `null` for the config in `createCore`) which overcomes the initial issue outlined in this case, but...

Hi @Viish I've gone ahead and just did a small reproducible project to confirm it wasn't any interference with anything else in the main app, and the issue still happens...

> Hi @ParticleCore, > > There is obviously something "wrong" (in the sense that it does something differently than we do) in the way you use our SDK, or there...

Thanks, I tried replicating the scenario with the Linphone app and the issue does not occur, the account is correctly removed from the config app even after closing and opening...

@Viish I see the tag was removed, did you manage to replicate the issue with the sample app?

@Viish yes, I only used bare min in the sample app, I did test with all the suggested methods before and the result was the same, but thank you for...

In the provided tutorial the `core.start()` is being used in the same way as I am using it, at the end of the account creation and all the parameters: https://gitlab.linphone.org/BC/public/tutorials/-/blob/master/android/kotlin/1-AccountLogin/app/src/main/java/org/linphone/accountlogin/AccountLoginActivity.kt...

> I simply added `it.start()` inside > > ``` > getFactory()?.createCoreWithConfig(config, appContext)?.apply { > isKeepAliveEnabled = false > isLimeX3DhEnabled = false > }?.also { _core = it > it.start() >...