SignalR events not coming in Android app built with TFS - android

I am using SignalR for one of my android projects.
The same project source control is under TFS (Team Foundation Server).
I integrated SignalR as mentioned in this answer Steps to get SignalR working in Android Studio
When I build the app using Android Studio, SignalR events are coming in the app.
But when I build the app using TFS build system, the events are not coming in the app. Though I am getting logs in the TFS debug build that the connection is success. Events logs are not coming.
What I tried:
I tried replacing the signalr-client-sdk-android-release.jar with locally built aar. But the result is same.
What am I missing?

Related

Why or what is the need to import unity android games to android studio?

I have experience programming in android studio and new in Unity. I have made a game and was able to ran it in my phone through unity without the use of android studio. So i though to myself that android studio wasn't needed when developing android games in Unity. But I see some people in the net wanting to import their unity projects to android studio. I got curious and wanted to know why they wanted to do that and if there are any features that android studio can provide that unity cant and vice versa?
There are many reasons:
1.Protect Unity project and its code:
When you perform a contract work that doesn't require you to provide the source code. You can use this to make sure that client has the Android Project only so that they can sign it. With this, client won't have access to the Unity Project and therefore cannot modify or release game for other platforms without your permission. You only release the Unity Project if client paid for that.
2.Embed Unity App in existing Android app:
When you already have an Android app and you simply want to show the Unity game through your Android app.
3.Gradle:
When you need to to perform tasks on the Android Project during automated build.
4.ProGuard:
When you need to obfuscate your code.
There are many other reasons but the ones listed above are the most reasons to export app as Android Studio Project.

Android App Crash: Running demo NaCl app (pexe app) on mobile using Apache Cordova

I'm trying to run a Chrome App on Android Mobile using the instructions from:
developer.chrome.com/apps/chrome_apps_on_mobile
From above URL, I could run the calculator app fine in Android Emulator 5.0.1 fine. No issues.
github.com/GoogleChrome/chrome-app-samples/tree/master/samples/calculator
Chrome App Calculator on Android Screenshot
Then I tried running the "Native Client" App on Desktop from example api directory of nacl_sdk:
developer.chrome.com/native-client/sdk/download
nacl_sdk comes with few examples including demo and core api examples. All examples works fine on Desktop. Out of them I took 'file_io' api example which runs fine after compiling (make). I took that folder and used the following command to create cca cordova app:
cca create FileApp --copy-from=/path/to/file_io/manifest.json
Then cd to FileApp and cca prepare
After that ran Android eumlate command:
cca run android --target=avd5
It processed everything fine, and I see no errors building this cordova app like calculator app. But, after 'LAUNCH SUCCESS' when the app launched the Android emulator crashed. The emulator windows closed.
I started the Android Emulator from AVD Manager, and after booting up Android I tried starting the 'File I/O' app, which in result showed me the message
"Unfortunately, File I/O has stopped." Screenshot
Does that mean the PNaCl/NaCl apps still are not supported on Android OS?
The NaCl app contains the .pexe file.
Is there any step in between I could be missing?
I'd really appreciate any help in this regard to test if I could run Native Client Apps on Android OS just like the Chrome Mobile Apps using Apache Cordova examples work.
Native Client (NaCl) isn't supported in Chrome for Android (and by implication the Chrome/Chromium based WebView).
See: http://developer.chrome.com/multidevice/faq
Q: Does Native Client work on Chrome for Android?
A: It does not, and we have no plans to announce at this time.
But then the OP read at: https://github.com/MobileChromeApps/mobile-chrome-apps/blob/master/docs/faq.md#is-nacl--pnacl-supported
Q: Is NaCl/PNaCl supported [in Cordova]?
A: No. However, you can still compile and use native code
by writing a custom Cordova plugin.
And unfortunately the word native is an overloaded word with different meanings depending on context, so the OP started asking about the Android Native Development Kit (NDK).
The Android NDK which uses Java Native Interface (JNI) for C/C++ code to communicate with the Android Java framework. Typically Android apps only use the NDK if there is need to port existing C/C++ libraries or have a computational performance requirement like physics modeling or image processing.
When Cordova is referring to 'native code' its referring to code written in Android Java which would need to be bridged via a Cordova plugin to the JavaScript side.
And of course why to use any of the above frameworks/APIs depends on what the OP wants to do.

NoClassDefFoundError on generated client library - GAE cloud endpoints

I have 2 endpoints in my GAE Java project. When I use the GPE eclipse plugin to generate the client library for my Android project, the code is generated without any errors. (I don't know why the generated code is in the package com.google.api.services).
The problem is, when I launch my Android app, a NoClassDefFoundError is thrown for the class, DeviceInfoEndpoint$Builder, and the app crashes.
This is after I updated the ADT and the GAE plugin to the latest
version. It was actually working well before that.
I even tried with the endpoints.sh script to generate the client library. Getting an EntityExistsException on that. I am literally struck now.
Any help would be appreciated.
After more than 2 days of dead stop, found out that I needed to check Android Private libraries and Android 4.2 in (Build path -> Configure build path -> Order and Import).
https://stackoverflow.com/a/16784945/902572

Test-Driven Development (TDD) using Xamarin and StackMob?

I am interested in using StackMob as my BeAAS on a project using Xamarin to create an Android and IOS version of my mobile app. I am using the StackMob.NET solution from
https://github.com/ermau/StackMob.NET.
I was successful at running the demo from the Android emulator however, I am unable to make successful contact to StackMob via NUnit (Visual Studio or Xamarin Suite).
Is this because I am not attempting a connection from within a mobile View? Or is it possible to create test methods that can connect to StackMob?
Also, has anyone tried integrating StackMob with Xamarin or .Net?

AppEngine Connected Android Project not working after update

I updated my SDK tools and SDK platform tools to the latest and to my horror found that AppEngine Connected Android project's emulator not launching if I do Debug as > Local AppEngine connected Android Project.
I am working on a project and also have done quite a lot of work using this plugin option. Is there a way that I can still develop. Maybe someway I could start the AppEngine Seperately and Android Project Separately and still they would work( debugging as remote AppEngine is not a problem).
To what I have read, I think they doing it because they are deprecating C2DM messaging. And instead they bringing the option of Make AppEngine Backends. But unfortunately they have still not worked on the docs or support.
Is there any way I can still keep working till they release the docs or how can I make the transition myself?
Here is how I debug localy since the sdk update:
Debug the app engine project as Web Application
Run the AVD with the manager
Debug the android project as Android Application
Remotely:
Run the AVD with the manager
Run the android project as Android Application
Hope this helps.
Edit:
After debugging remotely it seems that the AVD still speaks to the remote server eventhough you wipe out data and ask for "Debug android project". In this case do a "Debbug as local app engine connected android application". This will start the local server but not the Android app. Then Debug the android project as Android Application and it will talk to the local server.

Categories

Resources