My NFC application works fine in Android 12 and previous versions but fails in Android 13.
I could read tag header info but write to NFC tag send request and fails to read back response. I could not find any updates on NFC from Android release notes.
appreciate your support.
Thanks
tried checking in multiple android 13 devices, issue is same
Related
I am trying to enroll a fleet of Android 5.1 devices which did never receive a newer version of Android and are not working with any third party ROM. So we're stuck on 5.1.
As the Google Play Services in the ROM was so old, that I couldn't even install the Android Device Policy DPC, I updated the Play Services in the ROM using an update.zip, wiped the device and then enrolled the device using a NFC tag.
Unfortunately, enrollment is not working, and I'm not even getting an error message. The DPC seems to set itself as the device owner, but no enrollment is taking place - the device does not show up on the API, and upon launching the DPC from the application drawer and clicking on the "Get started"-button, we always are presented with "Your system cannot be managed by this app. Please contact your administrator".
Well, I am the administrator and I have no clue, why this is failing.
Has anyone an idea, what the DPC is looking for before deciding that the device cannot be managed? Or how to get a more meaningful message out of the DPC?
The Android Management API doesn't support NFC provisioning on Android 5.1. It is only supported on Android 6.0 and above.
The documentation previously mentioned that 5.1 is supported, that was an error and we have now updated it.
I followed the documentation(https://parse.com/docs/dotnet/guide#push-notifications-setting-up-push) by Parse for sending Push to Windows 8.1 device. But, I am not able to get through the first step ie. "Installation". As per the documentation I followed , the channel should get registered instantly. I have enabled "Toast capable" within the Package.appxmanifest file in my Windows 8.1 Universal App(C#).
I have also authenticated the App by adding the Package Security Identifier and the Client Secret to the Parse.com Windows Push Credentials settings. But still no success. Can anyone tell me if I am missing anything or if Parse SDK is supported for Universal Windows 8.1 C# App.
I previously had Parse working for WP8 as per instructions here. So this is to say it is definitely doable, follow those steps there to see if you missed any steps.
Caveat
We are using Cordova, but I had to end up doing this part natively. It was working in December 2015 but mysteriously this year we had issues with Parse on all 3 device platforms (iOS, Android, WP8). I'm still spending time trying to figure out why WP8 just doesn't work now, can't even get the device to register to a channel anymore...
It seems that new ios 8 APIs such as Local Authentication run on ios 7 without crashing. Of course, the actual policy validation fails (gracefully without a crash), but given that the API is brand new in ios 8, how is it that the app does not crash upon calling this new API?
In the previous versions we had to do a check before calling a new API.
This is just speculation, but sometimes a "new" API was already available in the older versions of the OS, but has not been made available for developers outside of Apple. However, if you submit such an application to Apple there is a good chance that it will be rejected.
I am using IBM worklight 6.0 for building a hybrid application. My application is running perfectly on IOS 7. When I migrated the same code to Xcode 6 beta for IOS 8 build, only the splashscreen with loader came up and the app hangs. From the logs I saw that the application goes to skinLoader.html. None of the events are called.
To my curiosity I created a dummy worklight iphone environment and ran it on IOS8 and again the app got stuck on the splash itself.
I had a deviceready event on the html which was not called. So I am curious to know if there are other issues other than the userAgent issues with the worklight for IOS8.
It is a known bug in iOS 8 beta 1 in Cordova applications and it is expected to be fixed in upcoming releases.
Applications that use Apache Cordova/PhoneGap are broken due to a bug that causes the window.navigator.userAgent object to become undefined when window.navigator is replaced by a pure JavaScript wrapper object.
via
and it is already answered in this forum.
A fix for the stuck-at-splash is provided in an iFix release from September 18th via IBM Fix Central.
For more information please see this question: Worklight 6.1 and iOS 8
Scenarios:
If a user has already upgraded to iOS8 and the application got stuck on the splash screen, AFAIK the way to handle it is to either:
Uninstall/re-install the application from the App Store.
Install a newer app version (see below) from the App Store.
If a user did not yet upgrade to iOS8, it is best to use the fixed Worklight Studio to generate an updated app, increment its version and re-publish it. Then, Remote Disable the existing version and direct users to install the fixed version from the App Store; the fixed version should then continue to work after upgrading to iOS8.
i post this question because none of the solutions posted to
already existing threads helped for me.
today morning everything worked fin, i pressed on the Run-Button and
my iOS-Simulator stated out of Xcode showing my implemented App.
few hours later it shows this error-message:
"Xcode cannot run using the selected device. No provisioned iOS devices
are available with a compatible iOS version. Connect an iOS device with
a recent enough version of iOS to run your application or choose an
iOS simulator as the destination."
My Targets iOS SDK is 6.1
Under Summary i chose as Device an iPad (as before)
Under Summary i chose 6.1 as Deployment Target.
I have no "real" iOS Device at home so i always used the simulator.
As i said, since today afternoon not working.
what could be the prblem?