Revision history [back]

click to hide/show revision 1
initial version

There is no Config Service sample for Android so I am assuming you wrote your own application. As such the error message is fairly straight forward, there is no session for the Config Client to connect to. This is due to the Android application failing to place an API call to BindSessionPort).

When you advertised using the AboutFeature that port value that you enter needs to be used in the BindSessionPort API call prior to sending the About Annoucement. From our AboutService example for the Java Language Binding, there is this snippet of code that you will need to have in your application:

Mutable.ShortValue contactPort = new Mutable.ShortValue(CONTACT_PORT);

    SessionOpts sessionOpts = new SessionOpts();
    sessionOpts.traffic = SessionOpts.TRAFFIC_MESSAGES;
    sessionOpts.isMultipoint = false;
    sessionOpts.proximity = SessionOpts.PROXIMITY_ANY;
    sessionOpts.transports = SessionOpts.TRANSPORT_ANY;

    status = mBus.bindSessionPort(contactPort, sessionOpts,
            new SessionPortListener() {
        public boolean acceptSessionJoiner(short sessionPort, String joiner, SessionOpts sessionOpts) {
            System.out.println("SessionPortListener.acceptSessionJoiner called");
            if (sessionPort == CONTACT_PORT) {
                return true;
            } else {
                return false;
            }
        }
        public void sessionJoined(short sessionPort, int id, String joiner) {
            System.out.println(String.format("SessionPortListener.sessionJoined(%d, %d, %s)", sessionPort, id, joiner));
            sessionId = id;
            sessionEstablished = true;
        }
    });

Of course, replacing the appropriate values with those needed for your application.