Running on emulator

felix-d · March 13, 2017, 9:20pm

Hello,

I am running my app on real devices just fine, but when I fire it up on the emulator it crashes with this message:


E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.travellers.app.android, PID: 6747
java.lang.RuntimeException: Unable to retrieve device. Invalid device ID.
at com.backendless.async.callback.BackendlessCallback.handleFault(BackendlessCallback.java:28)
at com.backendless.async.message.AsyncMessage$FaultHandler.handle(AsyncMessage.java:83)
at com.backendless.async.message.AsyncMessage.handleCallback(AsyncMessage.java:41)
at com.backendless.core.AndroidCarrier$1.handleMessage(AndroidCarrier.java:37)
at android.os.Handler.dispatchMessage(Handler.java:98)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6077)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:865)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:755)

As this crash happens outside of my code, how can I resolve it? I want to prevent it from occurring on other devices. Is the problem that the Play Services are missing (they are missing indeed on that instance). And when I run it on my emulator with Play Services enabled, it works.

What exactly is it depending on? Can I expect your code to be running when a device can access my app through Google Play Store? (Because then they would have Play Services enabled, right?)

Thanks for your support
Felix D.

mark-piller · March 13, 2017, 9:25pm

Hello,

Check in the debugger is the following value is set:

github.com

Backendless/Android-SDK/blob/master/src/com/backendless/Messaging.java#L56


import com.backendless.messaging.DeliveryOptions;
import com.backendless.messaging.Message;
import com.backendless.messaging.MessageStatus;
import com.backendless.messaging.PublishOptions;
import com.backendless.messaging.PublishStatusEnum;
import com.backendless.messaging.PushBroadcastMask;
import com.backendless.push.GCMRegistrar;
import com.backendless.rt.messaging.Channel;
import com.backendless.rt.messaging.ChannelFactory;
import weborb.types.Types;


import java.util.ArrayList;
import java.util.Arrays;
import java.util.Calendar;
import java.util.Collections;
import java.util.Date;
import java.util.List;
import java.util.UUID;


public final class Messaging
{

If not, you can assign a value to that variable before making any of the API calls.

Regards,
Mark

felix-d · March 13, 2017, 10:38pm

Okay so I guess I have to create a unique device ID first, right? What are the best practices for that, and why doesn’t the API do that for me? Is all of that somehwere in the docs?

mark-piller · March 14, 2017, 1:50am

Backendless assigns one as you can see in the code right here:

github.com

Backendless/Android-SDK/blob/master/src/com/backendless/Messaging.java#L73-L105


private static final Messaging instance = new Messaging();
private static final ChannelFactory chanelFactory = new ChannelFactory();


private Messaging()
{
  Types.addClientClassMapping( "com.backendless.management.DeviceRegistrationDto", DeviceRegistration.class );
  Types.addClientClassMapping( "com.backendless.services.messaging.PublishOptions", PublishOptions.class );
  Types.addClientClassMapping( "com.backendless.services.messaging.DeliveryOptions", DeliveryOptions.class );
  Types.addClientClassMapping( "com.backendless.services.messaging.Message", Message.class );
}


static
{
  if( Backendless.isAndroid() )
  {
    OS_VERSION = String.valueOf( Build.VERSION.SDK_INT );
    OS = "ANDROID";
  }
  else
  {

This file has been truncated. show original

However, I would like to rule out that something went wrong in that logic and that is why I asked you to check in the debugger if the value is set.

felix-d · March 14, 2017, 4:20pm

Hi,

actually … although having nothing changed the App now works. I mean I will not complain, but I am sorry for bothering you. I’ll let you know when it comes back one day. In that case: should I comment here or create a new question?

Thanks anyways (and for the links)!

Felix D.