When I try to sign an Android app, I first get an error:
"sun.misc.BASE64Encoder"If I try again, I get this error: "Could not
initialize class com.adobe.devtech.tools.JarSigner"I'm not sure if this
is an issue on my side, but we would really like to get this app updated
ASAP.Thanks for any help!
We're getting this error on some of our articles:Is there any additional
information about what this is referring to? Is there a page limit? Is
this referring to number of referenced files (images?) or size?Thanks!
I think the issue brought up in this discussion is that Navto hyperlinks
cannot be used to create the, very imaginable, flow of going back to the
parent in the content structure.Is there a way to do that that we are
overlooking?
Our tests show that "swiping from the left side" is not something that
our users intuitively try. (Although once they are taught, it's very
nice and easy)Is there a recommended way to indicate or teach this
gesture? (preferably without text since we're working in 13
languages)Can you still create a one-time "welcome screen" for
apps?Alternatively, is there any approximate timeline for when a button
that links to the current collection's browse page might be available?
