`app.appId` is this safe to use as a consistent vault identifier?

Hello all,

As the subject says, is the app.appId a safe identifier to use or does this change per instance? Is it the same for desktop and mobile device?

Or is this an undocumented unstable identifier that might go-away?

~ R

It’s not shared between devices, mobile and desktop use different methods for the generation of the appId.
As with every undocumented function/variable, it could get removed at any point.

What are you trying to use it for specifically?

Hey,

I need a consistent identifier for each vault where my plugin is being used. It needs to be consistent because I was looking to use it as part of my HKDF. I can’t use paths, names or other things since these could change, meaning all the key derivation functions would then fail.

It’s no biggie, I’ll just have to store one in my own settings for each instance, I was just wondering if there was a consistent identifier I could use that the user cannot change or influence.

If you could add some kind of vault-level consistency ID, that would be awesome though… and I would buy cake.

~ R