Is there any known issues with Samsung Galaxy 4 and Cordova?

Brandt__Lars · ‎03-06-2015

Hi

After changing from legacy to Cordova build I have a problem on a Samsung Galaxy 4 10.4 LTE. When the user starts the App, he just get a message telling him that the app was stopped. The app is running on a wide variety of Android phones with no problems, so it seems to be a problem specific to the Galaxy tab.

I tried building for Crosswalk, but the result is the same (tried both ARM and x86).

So any idea why only Galaxy Tab is affected, and what I could do to make it work?

Regards

Lars Brandt

Swati_S_Intel1 · ‎03-06-2015

Which android version are you running?

Are you using any AJAX code in your app? Or CSS transformations?

There are some known issues with webview in galaxy 4. The async activity problem was specific to Android 4.2, if you have version higher than that it should be okay. See this post : http://developer.samsung.com/forum/board/thread/view.do?boardName=General&messageId=246738

Other possibility is if you are using 3D transformation.

Swati

Brandt__Lars · ‎03-09-2015

Thanks, but Android version is 4.4.2, so I guess it is not related to the specific webwiew problem mentioned.

Today another user called with the same issue on a Samsung tab 2 with Android 4.2.2.

I tried to do a legacy build, and this app installed an ran fine on the Samsung 4 tab, so that's a temporary solution.

The only 3. party elements in the app are "https://maps.googleapis.com/maps/api/js?v=3", "BackgoundGeolocation" and "UniqueDeviceId", but they are not my main suspects, since the app runs fine on a wide varierty of Android phones.