I've just released my first publication on ipad and Android.
However, it seems that on an Asus TF300 Transformer it fails. I tried different Asus TF300's and gives the same result.
- App (viewer) downloads
- Library comes up
- After download of the folio, the whole thing crashes. Without any warning, error message or whatever, it just disappears. Restarting the app will not even get back to the library.
I thought this was specific to my folio, but it turned out other DPS publications suffer the same. As Asus is marketing this transformer-thingy a lto, I fear there will be more users who cannot use any DPS publication. It is of course not good for my reputation nor Adobe's, let alone my client's!
The Adobe Viewer also shows the same behavior.
Maybe it's Asus, but other apps seem to work fine on the TF300, although the standard browser seems to give have some issues.
I've tested my app on many other devices while running around city center and installing on tablets, they all work fine.
Can anybody confirm this? Did anybody experience the same and came to a solution?
for first I am sorry for my bad English. I am from Czeh Republic.
I have Asus TF300 and I have the same problem too. Android version 4.1.1. If I had ICS everything was OK. I need DPS apps. I have tried reinstal app, but the situation is still same. Does anybody know where is the problem?
Thanks for your replies!
If I want to use V23, I also need the Adobe Viewer to view the results: I've been told (we're having the folio produced through a reseller) I can not review anything in V23 because the viewer is not updated yet. And updating a folio to can not be undone as far as I know.
Next to that: we need to pay for every folio download. I do not want to pay for a download on a device where it does not work! How does Adobe handles this?
You can create your own custom Adobe content viewer to review content using DPS APP Builder. You do not need to wait for Apple's approval. Also even if you download latest viewer Builder and build a V22 App, that would also have the fix implemented.
OK, I've been misinformed on the viewer version not being available: I'll let them know
If I understand correctly, this is what needs to happen:
- I update the folio to V23
- I need to update the viewer-app to V23
- EVERY user of the current app MUST update the app to view the folio now
- EVERY user must download the new folio, again
- I must pay again for every download: if all users would upgrade, this upgrade DOUBLES the cost (I must pay per downloaded folio, right?)
Am I correct on this?
We have 2 Android-Apps that don't work on serveral asus-devices plus galaxy nexus 7 running android 4.1.
The readers of our daily newspaper are quite disontent. We need to give them a date when the bug will be fixed at least.
I really do hope, this issue will be fixed in release 24 or sooner?
@ Isabell : The issue does not exist on All ASUS devices. DPS Apps built with V23 work on Galaxy Nexus 7.
You should create a 'new' build in Viewer Builder and submit an update of the app to Google Play.
Our Engineering is working actively on the issue with other ASUS Devices like ASUS TF300.
@Himanshu: Thank you. What exactly do you mean by "like ASUS TF300"? Display? Android derivat?
What about these devices - are they "like ASUS TF 300"?
- EeePad Transformer TF201
- Asus TF 700
- Motorola XOOM
Please, be more specific. This "solution" is not acceptable, this is for us and our customers 6 more weeks (in best case scenario) of losing money, geting users angry and so on. You should consider hotfix for this, not leting customers wait and wait for months.
Hi All, as per the latest update on the viewer crash bug on Asus Transformer, the bug has been fixed with R25. Please re-built your app to R25 and perform a quick test and let us know the result.
We are currently running V25. And the Transformer still crashes.
This is our bugreport
java.lang.SecurityException: No permission to prevent power key: Neither user 10170 nor current process has android.permission.PREVENT_POWER_KEY.
at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.ja va:1299)
at android.content.ContextWrapper.enforceCallingOrSelfPermission(Context Wrapper.java:418)
at com.adobe.dmp.viewer.bootstrapper.bridge.environment.FullscreenProper ty.set(FullscreenProperty.java:49)
at com.adobe.dmp.viewer.bootstrapper.AdtSocketBridgeClient.onRequestProp ertySet(AdtSocketBridgeClient.java:190)
at com.adobe.dmp.viewer.bootstrapper.bridge.SocketBridge.handleMessage(S ocketBridge.java:210)
at java.lang.reflect.Method.invokeNative(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit .java:789)
at dalvik.system.NativeStart.main(Native Method)
Does the Asus Transformer crash when you install and run Adobe Content Viewer? What about DPS Tips? DPS Tips (which is v24) works on all the Android devices I have access to--Nexus 7, Nexus 10, Galaxy 7, Galaxy 10, Xoom, all Kindle Fire versions. I've never used a Transformer.
We our self have no Transformer to test. But here are our customers send-in reports. The error is always the one above.
220.127.116.11.70378 is r25
18.104.22.168.66332 is v24 with hotfix
22.214.171.124.62670 is v24 withot hotfix
All loosely translated from german.
Feb 16, 2013
Crash during the end of installation of a folio
Jan 12, 2013
Crash at initial viewing of a folio
Dec 29, 2012
Dec 20, 2012
TF 101 After download and installation crash, like always
Nov 19, 2012
why does this still not function?
Nov 15, 2012
Download works. During installation the tablet crashes. After that the app does not load anymore.
Nov 9, 2012
After update the app loads again. Download has hickups and is very slow (10min at 50mbit). During the installation progress the app crashes after beeing in installation for about 5minutes. During the whole time the tablet is unusable (frozen).
Nov 6, 2012
App loads. Login, dowload (128MB) starts, long installation time. App crashes and is only able to start again, once I delete the data in preferences.
Nov 6, 2012
In one case its the TF 101 I guess.
In the other cases, based on context, it seems to be mostly the same person haven the error over and over again.
I will try to contact the users and see what I can get on information.
We've tested our app with v25 on TF 101 & Android 4, everything is ok. Our customers using TF 300 with the same result.
I can confirm this issue, with a V20 folio and the latest viewer on a Samsung GT-P5110, sporting CM10.1 (Android 4.2.2).
The stack trace is the very same as posted above, so I strongly suggest to look at line 49 in FullscreenProperty.java.
The permission referenced in the exception message, "PREVENT_POWER_KEY", is specific to CyanogenMod. I'll try to take a look at their source.
I didn't build a custom viewer. That's still only available on Mac, I believe? I used the Adobe Content Viewer available on Google Play to download unpublished folios from my Adobe account. I tried a few very simply ones, too. Every folio, whether interactive or not, crashes the app instantly after the first page is rendered.
I'm just learning this stuff at the university.
Do you have the latest Adobe Content Viewer (V25) then? You can download it from : https://play.google.com/store/apps/details?id=air.com.adobe.contentvie wer&hl=en
Also DPS may not be entirely compatible with non-stock OS like Cyanogenmod. Cyanogenmod is known to disrupt with functioning of alot of apps and in alot of cases blocks wi-fi access, in other cases, the apps crash.
Yes, I (re)downloaded this app multiple times. It'd be a shame if it wouldn't work with CyanogenMod, considering it's the most popular aftermarket Android firmware. I also haven't had any problems whatsoever with any other apps.
I'll take a look at the CM sources later today.
We'll it not really an issue with DPS, that's an issue that comes with Cynogen for alot of Apps including Non-DPS Apps. These mods are not approved by manufacturers and create compatibility issues. on some hardware+mods combo apps work, in others they dont since mods are not created for specific hardwares.
Again, I do not have problems with anything but the Content Viewer app. I'm sorry I'll have to say this again very clearly: The problem is Adobe-specific. Blaming it on CM isn't helping you or me or anyone.
I finally managed to get around to looking at the code. The PREVENT_POWER_KEY window flag has a constant value of 0x80000000, which probably has no meaning in vanilla Android.
The check which crashes the application is only ever invoked when this flag is set. Flags don't set themselves, so...
I think you are relying on an implementation detail – the fact that a value has no effect. Yet. This is really bad.