App implementing Parse Unity Plugin crashes on android device but works fine in editor

Question

I am trying to use Parse in my Unity game in order to implement high scores. My problem is that when I try to put the game on my android device to test it, the name of the app comes up different. It comes up as "ParseUnityPushSample" even though I have not changed anything besides adding the files that Parse gives me to use it. The build settings have not changed and it even shows that my package name is the same, yet testing it on a device has this result.

Testing it in Unity 5 works fine. The game loads as it should. This only happens when I try to put it on a device for testing.

Along with it changing the app name, it also crashes when opening. I get a prompt that says "ParseUnityPushSample" has failed anytime I try to open it on an android device.

EDIT:

Okay so I figured out a way to view some errors that occur when testing on a device. I get this error: "Unable to find unity activity in manifest. You need to make sure orientation attribute is set to sensorLandscape manually. UnityEditor.BuildPlayerWindow:BuildPlayerAndRun()" I have no idea what the issue is though since I have manually set the orientation for the activity to sensorLandscape in the Android Manifest.

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android" package="com.laserdeflector.sab" android:versionName="1.0.1" android:versionCode="1" android:installLocation="preferExternal">
<uses-sdk android:minSdkVersion="10" android:targetSdkVersion="22" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.WAKE_LOCK" />
<uses-permission android:name="android.permission.VIBRATE" />
<uses-permission android:name="android.permission.GET_ACCOUNTS" />
<uses-permission android:name="com.google.android.c2dm.permission.RECEIVE" />
<permission android:protectionLevel="signature" android:name="com.laserdeflector.sab.permission.C2D_MESSAGE" />
<uses-permission android:name="com.laserdeflector.sab.permission.C2D_MESSAGE" />
<uses-permission android:name="com.android.vending.BILLING" />
<application android:label="Laser Deflector" android:icon="@drawable/app_icon" android:screenOrientation="sensorLandscape" android:name="com.soomla.SoomlaApp" android:debuggable="false" android:isGame="true">
<activity android:name=".UnityPlayerActivity">
  <intent-filter>
    <action android:name="android.intent.action.MAIN" />
    <category android:name="android.intent.category.LAUNCHER" />
    <category android:name="android.intent.category.LEANBACK_LAUNCHER" />
  </intent-filter>
</activity>
<receiver android:name="com.parse.ParsePushBroadcastReceiver" android:permission="com.google.android.c2dm.permission.SEND">
  <intent-filter>
    <action android:name="com.google.android.c2dm.intent.RECEIVE" />
    <action android:name="com.google.android.c2dm.intent.REGISTRATION" />
    <category android:name="com.laserdeflector.sab" />
  </intent-filter>
</receiver>
<service android:name="com.parse.ParsePushService" />
<activity android:name="com.soomla.store.billing.google.GooglePlayIabService$IabActivity" android:theme="@android:style/Theme.Translucent.NoTitleBar.Fullscreen" />
<meta-data android:name="billing.service" android:value="google.GooglePlayIabService" />
</application>
<uses-feature android:glEsVersion="0x00020000" />
<uses-permission android:name="android.permission.READ_PHONE_STATE" />
<uses-feature android:name="android.hardware.touchscreen" android:required="false" />
<uses-feature android:name="android.hardware.touchscreen.multitouch" android:required="false" />
<uses-feature android:name="android.hardware.touchscreen.multitouch.distinct" android:required="false" />
</manifest>

8/10/15

I have come to learn that this may be an issue with Parse v1.5.2 although changing to v1.3.2 did not help with the issue I am facing either. I will update as soon as I learn anything more.

8/11/15

Updating to v1.5.4 did not fix the issue either. Still having problems with the android manifest with the same error message. If anyone has any idea please let me know!

Answer 1

In my case, just taking the Unity sdk was not the answer. In order to make it work I had to use what was in the Unity blank project and then I also deleted the android manifest that v1.5.2 included in the sdk. Doing both of these things allowed the app to work correctly on my android device.