But if you use Adobe font obfuscation and your bookid is a uuid scheme and then change it to something not uuid based (ie: made up of groupings of valid base-16 hex chars) you would intentionally be breaking the obfuscation.
If I change it to something that is a valid uuid identifier, then font obfuscation should work with the new id just fine.
Similarly, if your use IDPF obfuscation and change the id to something non-valid (say a null string) it can break IDPF obfuscation (the bookid need not be uuid for IDPF).
So that is why we asked which obfuscation method was being used (see the encryption.xml in the META-INF) and exactly what it was and what you changed it to.
Please provide that info so we can try to recreate the crash and get it fixed.
|