We have an app where we have custom authentication working. Users can
sign in and sign out successfully. We want everyone who signs in
successfully to have full access to all the app content, and those that
aren't signed in will have access to only some content.Since we don't
need to keep track of which authenticated users have access to which
content (since they all will have access to all content) is there any
way to "fake" entitlement without setting up an entitlement server?
Kirk, based on the info you provided, I did some more testing. It turns
out that links to public PDFs on a Web server from an HTML article do
work fine in an Android app, and if Acrobat Reader or other PDF renderer
is installed on the Device, the reader is launched and the PDF is
displayed. But, this doesn't work if the URL for the PDF is an HTTPS
url. And, to further complicate matters, some of the non-secure HTTP
URLs for some of our PDFs automatically redirect to HTTPS, which also
keeps the P...
I have several HTML articles that work great in AEM Mobile. But some of
them contain links that we would like to open in the device browser,
instead of the built-in app browser. Is there any way to do this?
I have InDesign and HTML articles that contain a link to a PDF on a web
server. When the link is tapped on an iOS device or the Web viewer, the
PDF displays fine. But on Android devices the in-app browser is
launched, but nothing displays. Setting the link to open in the device
browser works fine on both iOS and Android. Is this a limitation of the
Android in-app browser? Is there a workaround? I'd rather not use the
OK, I found the answer...here it is. Maybe this will help someone else
out. The "Bundle ID" field in Project Settings > Access > Entitlement &
Authentication apparently has be be filled in with the app ID. The text
by this field is misleading. It says that if you don't include the
bundle ID here, the ID from the app settings will be used. True, but
there is no way in the Desktop Web App settings to specify a bundle ID,
so it is required here for the desktop web app to work with entitlement.
I'm working with a customer where we have implemented a simple
entitlement server using the sample source code available here: Set up
an entitlement service for AEM Mobile appsThe signin process and
restricted distribution is working great on our iOS and Android apps,
but not on the Desktop Web Viewer app. When trying to sign in to the Web
Viewer app, we get a message that says "The username or password you
entered is incorrect". I've double checked that the entitlement server
is working by usin...
Back in the DPS Classic days, Adobe announced integration between DPS
and Salesforce. What ever became of that? Is there any connectivity or
hooks between Salesforce and AEM Mobile? I have a customer asking about
this. They would like to set up restricted distribution, and every one
in the company is using Salesforce, and they are wondering if there is
any way to connect the two.
Jay, your note prompted me to test this in another, simpler test app
that I have. And of course, it worked fine in that app! But, the levels
of nesting of the collections and articles are exactly the same as the
problem app. The only difference that I can determine between the 2 is
that the app in which I'm having problems the collection is not yet
published, where in my test app it is published and out of date. But in
both cases I'm preflighting. The other difference is that my navto link
As I mentioned in my first post, this is happening is custom preflight
app builds, built with version 2016.11.The problem exists on iPads and
iPhones, but not Android devices.I can verify that I'm using the article
name and not the article title. I've tried this with several different
articles, just in case there was some obscure problem with the article
name, or it was being miss-typed or something.In your tests, did you put
the banner on the browse page of the collection that you are linking t...
I'm pretty sure this is a bug:I have a banner with a link defined as
The banner is used on the "september_october_2016" collection browse
page. In this context, the link sends the user to the first article in
the collection, not the article named in the link.If I put this same
link on a banner in a different collection's browse page, it works fine.
In other words, it appears that the
Ashe, 1.2 worked for the iPhone dual orientation app.I did some testing
with 1.4 in a simple, fresh file with 2 breakpoints with just a single
orientation test app also, and couldn't get it to work there either. Did
all my testing on an iPhone 6 in case that matters.
FWIW, I was never able to get version 1.4 or 1.3 to work with content on
an iPhone. Worked great with the same HTML article on an iPad. I tried
all kinds of sneaky things to see if I could get it to work, but never
figured it out. I ended up using version 1.2, and that worked for the
project at hand.
This .mucow is working great for me, except when the article is viewed
on the iPhone. The same article works perfect on the iPad and Android,
but when viewed on an iPhone 6, the AEM Mobile "chrome" can only be
displayed with a "long tap" on the screen. Weird. FWIW, this is a
dual-orientation app on the iPhone. Perhaps that has something to do
with it? I guess I'm just checking to see if anyone has this working
successfully on iPhone dual orientation apps?
We need to embed an RSS feed in an HTML article. This is easy enough to
do, but I'm having trouble getting any RSS Feed to display properly when
the article is viewed in the desktop Web Viewer. The feeds work great on
iOS and Android tablets and phones, but the feed content doesn't appear
in the Web Viewer. The Safari debugger reports that it couldn't run
"insecure content from http://ajax.googleapis/ajax/services/feed/load?"
We're having the same problem...starting with 2016.9 build. See my post
here: Change in orientation behavior in Android apps Something, somehow,
changed with the Android build, but I haven't been able to find any
documentation or explanation about this. Bottom line, is that right now
all the Android tables that we've tested display browse pages as a large
Peter, I tested this last week, and had a similar experience. It didn't
work at first, and I even verified that the AEMM code was preset in the
Muse-generated HTML. BUT...then it all of a sudden began working, and
has worked ever since! Unfortunately, I was changing so many things at
once, that I'm not sure what the trigger that made it work was. However,
one (stupid) mistake I made is that I was mistakenly still using the old
DPS-era HTML Article packager, instead of the new AEMMobilePackager.a...
We previously had an Android app built with version 2016.5, with the
Tablet orientation set to landscape, and the Phone orientation set to
portrait. With this version, my Android Google Nexus 7 displayed the
browse pages in landscape. But when we rebuilt that app with version
2016.9, the Nexus 7 is seen as a phone, and displays the content in
portrait. The same thing happens on a Samsung Galaxy Tab A 9.7 tablet
and a Samsung Galaxy Tab E Lite tablet. 2 questions: 1. How can we get
the app to dis...
Nathan, I understand that the "create account" link on iOS is in the
"Account" dialog in the hamburger menu. However, here's the problem:
Imagine a new user is in the app, and they do not have an account and
are not signed in. They encounter some entitled content with the
lock.When they tap "sign in" from one of these screens, all they see is
the log-in screen below on iOS devices.In this case, they have no idea
how to create an account. They aren't going to know to go to the
hamburger menu and ...
We are creating an AEM app that uses V2 entitlement. I just noticed that
the sign in dialog for the Web Viewer looks like this:But the sign in
dialog for the iOS devices looks like this:Wondering why they are
different? Differences that matter to us:1. The tablet screen says
"Username" but the Web viewer says "Email Address" (We prefer email
address)2. The tablet screen doesn't have a link to "create an account"
but the Web viewer does. This is important. We need this.Is there any
way to make th...
It seems that there was a change in the quality of article and banner
images after the 2016.8 release. They are all display at a low ppi. The
same article images have been uploaded at a minimum of 2000px wide, and
look perfect on a retina iPad. But the Web viewer looks horrible. Same
problem in 3 different apps I've worked on for 3 different companies.
Was there a recent change in how article images are automatically
downsampled for the Web Viewer?For an example, see this
Way back in the DPS days, Adobe "opened" the .folio format, with the
purported idea that perhaps people would create other apps that could
consume and display folios. I'm wondering if there is anywhere that the
.article format is documented, and if there is any intent on it becoming
an open format?I have a customer that has asked if they can "wrap" their
AEM Mobile app within another "parent" app. I assume this isn't
possible, so I'm wondering if skilled programmers could create an app
Very helpful. Can't wait to try it! This has been on my "to-do" list for
a long time to figure this out, but now I don't have to. I know many
people that will find this very useful. Thanks for sharing!
I know there isn't any way to clone, duplicate, or copy a Project in the
AEM Mobile portal. But I'm wondering if there is any way that Adobe can
do this on the back end for a customer's account? I have a large
customer that has created an app with complex content and layouts, and
now they need to create a Dutch version of the app. The Dutch version
will use the same layouts, cards, and rules, but some of the content
will be different, thus the need for a second app and a second project.