The AEM Mobile signing tool supports either Java 7 or 8 due to
sun.misc.BASE64Encoder being removed in Java 9.For this reason you will
need a maximum of JDK 8 installed and set as the default JDK i norder to
use the signing tool.See: Java Platform, Standard Edition Oracle JDK 9
Migration Guide, Release 9
The missing splash screen image for iPhoneX is a known issue and a fix
is currently being implemented for an upcoming release of AEM Mobile.In
the meantime there is a workaround you could do.Unzip the downloaded
IPAShow package contents of JupiterReplace
'LaunchImage-1100-Landscape-2436h@3x.png' and
'LaunchImage-1100-Portrait-2436h@3x.png' with your own splash screen
imagesRe-zip the IPARun the IPA through the signing tool as usualAnthony
Hi Scott,Are you enterprise signing your app with the 2018.1 version of
the app signing tool?The 2018.1 version of the iOS viewer upgraded to
using XCode9 in order to better support iOS 11 which also required an
update to the signing tool as well.Anthony
Can you check the first project that appears in the target project
dialog to see if the layout appears there?As I mentioned in a previous
post there was an issue with the dialog where the target project was not
being selected correctly when the radio button was clicked. This has
since been fixed in today's production release.
Hello,The issue you are having may have actually been fixed as part of
the hotfix rollout to production today.The issue was dependent on where
you clicked on the target project dialog. If you clicked on the title of
the project the copy would work as desired. However, if you clicked on
the actual radio button the copy would always be made on the first
project in the list.As I mentioned this behavior has since been fixed
and went live a couple hours ago. The correct project should now always
be u...
Pages from a site cannot immediately be simultaneously used in an app as
well. The reason for this is because generally Pages are implemented
differently for an app vs. a site. If you still really want to have your
site simply wrapped in an app you could possibly employ your own custom
copy mechanism that takes pages from a site and copies them to an
app.Keep in mind however that assets can be shared across a site and an
app. This includes images, videos and even text with the new content
fragme...
HiYou will need to install a Cordova plugin in order to obtain the
device IMEI on Android. iOS doesn't allow the IMEI to be obtained. After
a quick search there seem to be a number of Cordova plugins that do this
already.Here is one example:
https://github.com/zho/phonegap-imeiplugin.I have never used this plugin
so cannot provide any opinion but feel free to try it out to see if it
suits your need.If you can get away without not requiring the device
IMEI there is also the Cordova device plugin ...
Hi there,This is specifically a mobile web issue and not related to
mobile apps. Have you followed the Apple documentation for web
clips?https://developer.apple.com/library/ios/documentation/AppleApplications/Reference/SafariWebContent/ConfiguringWebApplications/ConfiguringWebApplications.htmlAccording
to
(https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/MobileHIG/IconMatrix.html#//apple_ref/doc/uid/TP40006556-CH27-SW2)
the size of the web clip icon for an iPhone6S...
Hi Ravi,In order to download the source for your app for building with
the CLI you need to use the link on the PhoneGap Build tile. The
download button you are using under Manage App is just the iTunes meta
data that can be used with iTunesConnect for an app store submission.As
for your PhoneGap Enterprise App issue...are you getting the Undefined
[object:Object] error after entering your user name and password? Do you
ever get as far as seeing your list of apps?
Hello Sakshi, Is this the link you used to download the ZIP from GitHub?
https://github.com/blefebvre/aem-phonegap-kitchen-sink/archive/master.zipI
just tried this link on a Mac and was able to unzip successfully. If you
are using Windows you may be running into path length issues. This
sample includes all the required plugins [0] which results in some very
deep path structures that Windows complains about.Another option you
could explore are the samples over at
https://github.com/Adobe-Marketin...
Since this question has come up multiple times recently I've created a
branch [0] on the starter kit that explores this option. This branch
upgrades to ionic 1.1 and includes all the JS as well. The main issue
revolves around loading all the JS in the proper order. Currently the
branch solves this by using the version of angular that ionic uses in
its bundle instead of the built in AEM angular.js clientlib. I think
this could be cleaned up some more but to get started this branch will
result in ...
Hi again,You either need to explicitly include a clientlib on your page
or component or make it a dependency on another clientlib. Now that you
have your jQuery lib being successfully included in your ZIP you still
actually need to reference it on your rendered pages.In the case of your
splash page example above that would be adding a dependency to your
jquery category just like angular is added.Go to the properties for
apps/geometrixx-outdoors-app/components/splash-page/clientlibs and add
your ...
Hello Jose,Any clientlib you reference also has to be included in the
content sync config for your app. If you haven't done that yet the
desired library JS will not be included in the ZIP you download from
AEM.For example, this is how the Angular JS library gets added to the
ZIP in the starter kit example you
mentioned.https://github.com/Adobe-Marketing-Cloud-Apps/aem-phonegap-starter-kit/tree/master/content/src/main/content/jcr_root/content/phonegap/app_name_placeholder/shell/_jcr_content/pge-a...
The addition of emulators to the devices button is done deep within the
Sidekick JS code.There is a getPreviewPanelConfig() function that adds
the buttons and then getEmulatorMenuConfig() is called which looks up
pageInfo["emulators"] and iterates through the array.For some reason
your specific use case is causing an un-handled failure to occur on the
client. A bug may need to be logged if you are unable to solve the issue
on your end.
Well that is a little more odd then. If you are seeing emulators defined
in the JSON for the same page you are trying to preview then those
emulators should be showing up under the Devices button.It doesn't feel
like there is a bug yet but you could open up a web inspector in your
browser to see if any Javascript errors are occurring when entering
Preview mode. You could also check the network inspector to verify the
pageInfo.json that is requested for the page in question definitely
contains th...
Hi Jason,If you are seeing the Devices button with no drop down that
means CQ doesn't think the page is mobile enabled.You can test this out
by requesting
http://localhost:4502/libs/wcm/core/content/pageinfo.json?path=Do you see an "emulators" property in the returned JSON?If you
don't that means CQ doesn't think the resource type for the current page
is a mobile page.To verify this head on over to the OSGI web console
http://localhost:4502/system/console/configMgr and search for
"MobileEmulator...
Hi again Alex,The git hub project build dependencies have been updated
and the public Adobe repo was added as well. I also updated the Android
API levels while I was in there making fixes.You should now be able to
build and install the content package to AEM with any standard Maven
setup.As for building Android it is a little more complicated. I suggest
you follow the instructions here:
http://books.sonatype.com/mvnref-book/reference/android-dev-sect-config-build.html#android-dev-sect-repository...
Hi Alex,Thanks for bringing up the issues you are encountering with the
sample native Android app. I am going to look into the build issues you
encountered and will update the Git project.Did you follow the README
for setting up your local Maven environment for Android?This sample in
particular demonstrates how web content from AEM can be embedded into a
native app via a Cordova web view. If you don't want to access device
APIs you could also embed AEM web content directly into a native web
view...
Since this PDF is based on a LiveCycle Designer template individual
pages cannot be removed. Can you not just go back into Designer and
remove the page you don't want anymore and add in a new one?
Hi Kiran,Depending on what version of Acrobat 9 you have the bug
mentioned in this blog post may be the
culprit.http://blogs.adobe.com/livecycle/2009/03/post.htmlAlso, if you
have further questions there is a LC Designer specific forum that you
may find more
useful.http://forums.adobe.com/community/livecycle/livecycle_es/livecycle_designer_esAnthony
