I am a Google Glass application developer. During developing one application, I encountered some problems.
My application have landed on MyGlass and it's on review process, so it's not publicly visible. It only can be seen by me.
The problem is:
When I turn on my Glassware in MyGlass, my glass device never receive my application. Should I receive it or not? And why didn't I receive it?
I have launched the method mirror.accounts.insert.execute() from https://developers.google.com/glass/develop/gdk/authentication, and it didn't raise an exception, but I didn't receive the account information and the authToken on my glass device. This is because I haven't received my application on my glass device, am I right?
This is indeed correct: the token will only be sync'ed and available once the APK from MyGlass has been downloaded to your device and installed. After this first installation, you can safely replace the APK with a development one using adb install -r as long as it's using the same certificate.
Make sure to check that your device is connected to the internet, especially through WIFI. If that doesn't work, ask the Glass review team to help you out and check if there are any internal issues that would prevent your APK from being downloaded.
Related
I am testing WSO2-Emm system for managing our android mobile app. We have an app for taxi drivers. We deploy it using our tablets and a single gmail account. Our problem is that google allows up to 10 signed in devices for a single google account.
I have tried to load the apk to the WSO2 store. The problem is that when I want to upload a new version of the same app I get a warning message saying that this APK already exists in the store. When I try to rename it and add it as a new apk it works. The problem is that when I go to App-Management, the application appears under 'installed'. The Emm system doesn't detect there is a new version.
To be more specific, my question is is there a way to manage mobile application versions using the WSO2 store and not the google play store.
If there is a way we can go on with this system. If not, we will stop testing it.
The only way I've figured out how update an already installed app is by going to the App Management tab, selecting your latest version of the app in question, and hitting the install button under the Roles tab (NOT the Users tab). It will send the install command to any devices listed under roles you have checked, even if they already have the app installed. Keep in mind this will install the app on all the devices, even devices that already have the version you're trying to put out.
It looks like you already know about the patch on EMM-686 that must be implemented in order to upload multiple versions of the same app to the Publisher. Just in case you want to confirm it's implemented correctly, see my answer here for instructions on how to implement it.
I'm testing the implementation of the emm, and as i understood in the documentation i can
Automatically install applications WITHOUT end user intervention
Block any application to prevent its installation
Automatically UNINSTALL any app without end user intervention
I tried to perform this tasks using Policies but it didn't seem to work.
I'll appreciate your help.
Thanks.
Gabriel.
You need to configure WSO2 EMM in order to get it working. However for Android devices silent installation and uninstallation does not work until you install the Android Agent app as a system app in your devices. So it will prompt a message to user when EMM server perform an installation or uninstallation operation on the device. But for iOS it happens without use intervention.
if you blocking an app, EMM 1.0.0 shows an warning message to the android users to remove it. and for iOS it actually block the app.
You can use policies to block apps and install apps to the devices.
For iOS you need to configure it according to the documentation in order to get it working. For Android it works without any configurations, but if you are going for production you need to configure it.
I got around this issue by rooting the Android devices we're using and installing the Xposed Framework, along with the XInstaller module for it. There are several options for installation/uninstallation that can be used to create an installation/uninstallation experience free from the need for user intervention.
This was pretty easy for me to do, as we're only using corporate-owned devices that don't even leave the facility. Your mileage may vary.
In iOS6 I used to install some of my apps over an adhoc network without internet sharing. So the iPad had no internet connection. Therefore I use a typical html and plist file. Everything was alright.
Now, in iOS7 the installation is not working anymore. It is just stuck in "Waiting" and nothing more happens. (Note: It is still working on my iOS6 iPad)
First I thought something might be wrong with my plist, but then I copied the files to my IIS Server and installed it from there. Here I had a internet connection on my iPad and everything worked out.
Is it possible that the wireless distribution now needs an internet connection in iOS7 e.g. to check the ipa in the app store or something like that? Because this is the only difference I can see.
The app is signed with a valid distribution profile.
Thanks for your help.
It turned out the installation of apps over the air in iOS 7 really needs an internet connection now. The iPad tries to contact at least the following URLs before installing the app.
ax.init.itunes.apple.com: The device obtains the current file-size limit for downloading apps over the cellular network.
ocsp.apple.com: The device contacts this site to check the status of the distribution certificate used to sign the provisioning profile.
It seems in iOS6 it was ok if those URLs were not reachable and now in iOS 7 they have to be reachable.
Well i just had the same problem and I figured it out. At least on my xcode this is what happened. Turns out the application target release code siging identities auto set to developer and not their current state, from xcode 4.x, which is distribution. So when I went to distribute my application I kept getting the same error you had. So Click on your project name in your project explorer then click on the application target, not the project, and make sure the code signing identity is not set to developer for your releases. I have no idea why the code signing identities were automatically set to the developer profile, maybe there was some sort of bug when updating from xcdoe 4.x to xcode 5 that caused this. But now other devices are able to install the program. Hope this helps.
I have installed the apprtc python application in my linux server, its ok when trying to connect between browsers, but when I'm trying to create peer2peer with the apprtcdemo app for android, I get this error in my channel.html "the provided token is no valid", I see that when I change the android app url https://apprtc.appspot.com/?r= to a custom domain , its weird because if I just use the first url it works...
Could someone help me with that?
Tks very much
There are two android apk available for WebRTC, appRtcDemo and webRtcDemo. appRtcDemo apk can be used for android device to browser connectivity. You need to provide room id to connect to one room. If you are the room initiator then you have to enter -1.
If you want to connect two android device then you have to compile and install webRtcDemo apk. This apk interface provide place to enter ip address of another device and vice versa then both device will be connected.
Please go through http://www.webrtc.org/reference/getting-started for more information. Both the apks i've compiled and installed and checked how it works.
I'm getting a "new" kind of error in the provisioning hell from iPhone. Does anyone have an idea what's going on .. because reinstalling , redownloading of the profile doesn't work.
I've uploaded a screenshot.
http://img94.imageshack.us/img94/1559/picture15f.png
So the part where it says cannot be installed on devices?
If that is your distribution certificate (as your title implies) then the error message is correct. Distribution certificates are only for submitting applications to Apple for review.
Instead you will want to install a development certificate on your phone. That will allow you to load your phone with your own code for testing before submitting to Apple.
I would absolutely call it hell. Signing my first app for Apple is taking 100 times longer than it took for Android. I'm not quite sure why such tight security is needed. I've been spending an entire day on this security stuff. I'm sure once I figure it out it won't be too horrible, but this is a real pain so far.