Is there a possibility with the Android SDK to check the NFC "Secure Element" location currently set on the device? For example "Auto, Android OS, SIM"
Ok I found some Android documentation,
https://developer.android.com/reference/android/nfc/NfcAdapter#EXTRA_SECURE_ELEMENT_NAME
looks like its possible to get Secure Element name.
Related
I am interesting in writing an url to NTAG215 cards, so far I have download some apps for Ios tagwriter and NFC tools however once I try to read the card I have to open the app and read it, and my intention is to approach the phone and it will be able to pop up the window that let me open the link.
I have read and search quite a bit online about this but I am confused if this is something that needs to be develop using a sdk or its something the I have sort it out playing with the phone configuration.
any information will be much appreciated.
JL
So iOS does support some background processing of URL's in the correct form.
See https://developer.apple.com/documentation/corenfc/adding_support_for_background_tag_reading
If you look at the NDEF spec https://github.com/haldean/ndef/blob/master/docs/NFCForum-TS-RTD_URI_1.0.pdf and look to only support URI Identifier Code 3 & 4 and possibly not 1 & 2
And from Apple's doc's
Note
Background tag reading doesn’t support custom URL schemes. Use universal links instead.
Definitely not URI Identifier Code 0 (custom URL)
And NXP Tagwriter App seems to default to "custom URL", so try writing the URL using the https:// or http:// from the drop down menu.
We are developing PWA for our app because it's capable of 99% of our needs , however we do need NFC reading capabilities (not writing) and we would hate to abandon PWA and go Native just for this 1 thing
Our purpose for NFC is for reading the serial only. In fact we dont need fancy NFC functions. We just have a text field where the NFC code should be typed in, kinda like how barcode readers work (keyboard emulation)
Is this possible with PWA today?
The Web NFC API has a draft status at W3C. However, it seems to be the case that Chrome for Android has support for NFC, but only in experimental modus.
This means that currently, if you would release your application today, NFC will not generally be supported. However, the fact that Google has it available in experimental modus, seems to indicate it will be more widely available soon.
You can check the status here
For in-house solutions (or solutions where you have full control over the device) you can do it without NFC api in browsers (at least until it is available).
You will need to install Tasker app (paid, about 3 USD), which can create NFC read trigger, which then can open url like yourapp.com/{nfc_uid}. If YourApp is installed as PWA, you can select to open the url in the app instead of browser. This way it will look like the PWA is reading the NFC tag.
To make it work:
1. Install Tasker
2. Add new -> Event -> Network -> NFC Tag. Leave field blank and confirm (or just press back button)
3. Add new Task to this trigger: System -> Send intent
Action: android.intent.action.VIEW
Data: http://yourapp.com/%nfc_id
Extra: com.android.browser.application_id:yourapp
Target: Activity
4. Save
The reason we are not doing it using Task "Open url" is because we do not want to open new tab each time it is triggered.
If you have everything right and you scan NFC tag, your app should load with the NFC UID in url.
I think that you have any solution, if you don't have solution yet, so I recommender check this web site.
https://www.chromestatus.com/feature/6261030015467520#
https://googlechrome.github.io/samples/web-nfc/
to enable NFC experimental on Chrome type chrome://flags on G Chrome Android explorer
I want to have a section in my app that shows the device type so I can make it noticeable to show that the device is supported. How do I get this? I tried
UIDevice.currentDevice().
and there was no platform type.
Why cant you use:
UIDevice.current.systemName
That worked for me.
You should check this Question here.
I didn't get why you want to show the user if the device is supported.
The user shoudn't be able to download your app if the device is not compatible, and you can limit what device can download your app by doing this.
This link can also help you decide what UIRequiredDeviceCapabilities key you should use
When I try to write my custom app, I am asked to white list the device. But how can I run the sample apps without whitelisting my chromecast device.
Sample apps here, https://github.com/googlecast/CastHelloText-android
First you need to add the app on your Google Cast SDK Developer Console. Once it is added, click on your application and publish the app. As stated:
When published, your application can be launched on any device. When
unpublished, your application can only be launched on your authorized
devices.
If you want to use your own receiver, you have no choice but to whitelist your device for your app (unless you decide to publish your app which is not a good idea). You can use the app id that is provided in that project and that refers to a published on but that is not your receiver anymore.
I have made an app, and tested it fully on my phone. When I uploaded it to the market, it says it is incompatible with my phone - why is this, and is there any way to manually include my device?
It turns out that because I had set my app to use the protection (App-Private data folder), it wouldn't be installed to rooted phones. My phone is rooted.