Friday May 03, 2013

Why should you move to 11.1.2.4?

Hi, everyone:

It's great to see our engineering team has come through and delivered a bunch of new functionality in just a few month, since the release of ADF Mobile 11.1.2.3 in late October of last year.  As Shay blogged about the new features in the previous entry, there are plenty of reasons to move to the new version.  Many of developers in the ADF Mobile community has been looking for ways to push real time notification to ADF Mobile applications, or looking for ways to properly display file content on both iOS and Android devices.  11.1.2.4 now provides these functionality.

One great fact about the new push notification support is that native capabilities are used.  This means you would leverage Apple Push Notification Service or Google Cloud Messaging Service to push notification to ADF Mobile applications.  There is no proprietary or specialized messaging application you would need to implement - you can directly communicate with these push notification services with any backend servers.

File display support is critical for any application that needs to display file content.  In the 11.1.2.3 version of ADF Mobile, you would leverage a LocalHTML feature to display files on iOS devices, but there is no solution for Android.  If your application needs to display file content such as PDF or Word document, you should migrate to 11.1.2.4.

Another great feature is "Application Archive" support.  This is a great re-usability feature for ISV or SI partners - partners can simply create an application archive that includes all application artifacts and re-use the application in different engagements.  For each individual customer, the SI partner or customer themselves can extend the application archive with new functionality, and deploy it within their enterprise.  This is also needed if the customer needs to sign the application with their own certificates and profiles, as needed by most third party Mobile Application Management packages.

Lastly, there are numerous performance enhancements  - for example enhancements around ListView performance.  

Instruction for migrating an application to 11.1.2.4 is documented in the Migration Section of the ADF 11.1.2.4 Release Note.

However, there are also a few other important reason to move to 11.1.2.4 now - please review these carefully and see if they apply to you:

  • Apple has stated that, as of May 1st, 2013, all apps submitted to the app store must properly support the iPhone 5 form factor.  iPhone 5's screen size is 1136x680 pixels with a 16:9 ratio, where as previous iPhone screen size is 960x680 pixels with 4:3 ratio.  Similar to all apps developed before iPhone 5 was released, ADF Mobile apps developed using 11.1.2.3 would be displayed in letter-boxed format.  This no longer meets the updated Apple UI Guidelines.  Therefore, if you are planning to submit an ADF Mobile application to the Apple AppStore, you must move to 11.1.2.4, which has proper support for the iPhone 5 form factor.
  • 11.1.2.4 also adds support for iPad mini - allowing you to specify icons and splash screen for iPad Mini.
  • If you wish to test using iOS6 simulators that comes with Xcode 4.5 and above, then you must move to 11.1.2.4.  There is a known issue with application unable to rotate even if the device is rotated.
  • JDeveloper and ADF Mobile 11.1.2.4 have been certified to work with more recent mobile SDKs (i.e. Xcode 4.5/iOS 6 and latest Android development tools/SDK).  Therefore, if you wish to use these new SDKs, you should move to 11.1.2.4.
  • There are many bugs fixed in 11.1.2.4 - if you are currently encountering any bugs in 11.1.2.3 version of ADF Mobile, check out this list of bug fixed.

On behalf of the entire ADF Mobile development team, we would like to THANK YOU for your continued support of ADF Mobile.  We would definitely like to hear from you.

Joe Huang


Wednesday Oct 31, 2012

Workaround for an Xcode/iOS SDK Issue...

Hi, everyone:

When you are doing ADF Mobile development, and you need to deploy the application to an iOS device, you would need to compile/deploy the app with iOS App Certificates and Provisioning Profile. This means you would need to "Deploy to Package" or "Deploy to iTunes" during deployment, and configure JDeveloper with the proper certificates/profiles. In some instances (exact combination is still not clear), deploy and signing the application to generate the ipa file may fail with similar error message at the end of the deployment log:

[01:04:45 PM] Deployment failed due to one or more errors returned by '/usr/bin/xcrun'. The following is a summary of the returned error(s): Command-line execution failed (Return code: 1) error: /usr/bin/codesign --force --preserve-metadata=identifier,entitlements,resource-rules --sign iPhone Distribution: Oracle Corporation --resource-rules=/var/folders/x7/21sjrpx13qj9tq20z14s3j_w0000gn/T/tkROhP11qU/Payload/HelloWorld.app/ResourceRules.plist --entitlements /var/folders/x7/21sjrpx13qj9tq20z14s3j_w0000gn/T/tkROhP11qU/entitlements_plistEINPBkIG /var/folders/x7/21sjrpx13qj9tq20z14s3j_w0000gn/T/tkROhP11qU/Payload/HelloWorld.app failed with error 1. Output: /var/folders/x7/21sjrpx13qj9tq20z14s3j_w0000gn/T/tkROhP11qU/Payload/HelloWorld.app: replacing existing signature Program /usr/bin/codesign returned 1 : [/var/folders/x7/21sjrpx13qj9tq20z14s3j_w0000gn/T/tkROhP11qU/Payload/HelloWorld.app: replacing existing signature

This issue is a known issue and is not related to ADF Mobile. The workaround is discussed in this article from StackOverflow.

This article refers to the old location of Xcode, so you would need to adjust the paths accordingly. The path for Xcode 4.3 and above would be like:

/Applications/Xcode.app/Contents//Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/PackageApplication to this script file.

To modify it, you probably can’t use Text Editor. I end up opening a terminal session, changed the file permission, and used vi to update it.

Thanks,

Oracle ADF Mobile Product Management Team

Monday Jun 25, 2012

Oracle ADF Mobile and Developing On-device Mobile Applications

Hi, everyone:

It has been almost a year since we posted to this blog, and I am happy to report that we are steadily marching toward releasing a new generation of ADF Mobile.  This blog site has been quiet as we are heads down to develop this new generation of ADF Mobile.  As we are nearing releasing this next generation product, there are substantial number of Oracle internal application teams and external customers/partners actively developing using the beta version of this framework.  We are actively taking feedbacks from these teams and ensuring the product is ready for general availability.

If you are intersted for more details around this new generation of ADF Mobile, we are hosting a session and a hands on lab this week at the ODTUG KScope 12 conference.  The lab is booked completely full weeks in advance, but perhaps you can still get into the session (Wed at 9:45 AM).  

Look for updates from this blog site as well as the Oracle OTN ADF Mobile landing page during the weeks leading to Oracle OpenWorld 2012.  

Thanks,

Joe Huang
About

This blog is is dedicated to tips and tricks for developing, integrating, securing, and managing mobile applications using Oracle Mobile Platform. It is created and maintained by the Mobile Suite/Oracle ADF Mobile product development team.

Archive of past entries

Even More Mobile Development Blogs

Oracle A-Team Site - Mobile Related Entries

Code samples from the Community

Fusion Middleware Blogs

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today