I am working on a mobile application for Microsoft built in React Native . This app uses Microsoft login for authentication. I was able to run the app fine in the emulator without enrolling the emulator to intune ( the computer is intune compliant ) . Suddenly Microsoft has mandated intune enrollment even for emulators , now I cannot login into the app on emulator .
I even tried to enroll the emulator to intune but it will simply ask me to "Reinstall company portal" in a loop . Also, iOS simulator doesn't allow intune installation . Please advise how I can continue development.
I even tried to enroll the emulator to intune but it will simply ask me to "Reinstall company portal" in a loop - I suppose this could happen due to conditional access. Have you checked the sign-in logs what it says about conditional access? It looks like you guys are enforcing enrollment when it comes to native app
Also, iOS simulator doesn't allow intune installation - have you check if you can enroll the ios (not the emulator)? Also check the sign-in logs if it did failed just because the conditional access or it could be enrollment device platform restrictions
hope it helped
Related
Scenario:My app is working fine in mobile device after connecting with NordVPN.When the same App When I execute in Andriod Studio emulator after connecting with NordVPN,the App is launching but at one of the page the dropdown is showing error,rather than the values.
Requesting if someone can help me to resolve the issue or can provide any supportive link.
I have recently find the solution by first wiping out the data and then reboot refactory the android emulator in android studio.
We have developed an app using Xamarin Forms which targets iOS, Android and Windows Phone. We are using camera feature to take/select photos to be uploaded to the app and the feature works well on all three mentioned platforms.
We have some users facing issues on few windows devices. When a user tries to download the app from Windows App Store, they receive following error:
"This app is not available for your phone because it requires front facing camera”
I have attached screen shot showing the error for reference. The screen shot is taken from Nokia Lumia 635. Our finding that this device has only back camera, no front camera and we believe this might be the reason for above mentioned issue.
Ideally, users should not get this error as this device has back camera and they still can get the photos.
Is this a known issue in windows phone world?
Can this be fixed from code, device permissions?
Is this a device specific problem?
Any ideas?
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 new to windows phone, and I don't have a real device to test on.
I know that one can install .XAP files from SD card.. but does this process reqires internet access to check that the app is on the store or I just installs it as in Android?
Thanks in advance
You can debug your app on your physical device in Visual Studio. Your device has to be connected via usb cabel to your computer and has to be developer unlocked. You can developer unlock your phone with the Windows Phone Developer Registration Tool, which is a part of the Windows Phone SDK. You can find more information about the process here.
No, you cannot install the xap package on other people devices until unless their phones are not developer unlocked. When you build a .xap package in Release mode, you need to first upload it to Store where the Microsoft team checks package for security concerns. Once that has been checked, package verified, then the packages can be installed, basically uploading the app.
To debug the app, its better to unlock your friend's phone and then test it on it. After that if you wish you can also un-register the phone to revert back to original developer locked mode.
There is one more method which I use when my app is completed but do not wish to release the app on store, but instead, I wish that first these apps be used by my friends first, they give feedback and after that I finally submit the app on Store.
To do this, I submit the app in private visibility on Store. There is an option while submitting the app which indicates whether you want that other users can see your app on phone. I mark it Hidden. Once my app is verified and is on store, I download the app from store by going to the appropriate link of app on store which is given in app profile at dev-center. I choose 'Download and Install Manually' option to download the xap. This xap can be installed on other devices without unlocking their device.
I have created a APP using GCM which works correctly on Android platform 4.1 and 4.03 (I.e. Gets a RegId and register itself in my server and can even recieve a GCM), but when I start the emulator for android 2.3 (API 10) then the app gets installed but never registered I.E never gets RegId. When I start (install) the application for the first time then it receives a GCM message which I do not understand where it comes from but I can see that the device is not registered in my server. I also used a HTC phone with 2.3.3 android software and stil same result. Can any one see what the problem might be?
On the emulator it should normally not work, because it will not have a google account tied to the device. It is requiered for a device to have a google account and Google Play installed to register for an id.
The phone on the other hand should work.
GCM will Work from Android 2.2.
Refer this tutorial it may help you,
http://androidv5.wordpress.com/2012/08/15/how-to-implement-google-cloud-messaging/
it works fine for me.