Forum Replies Created

  • Re: Reply To: Registration failed on Famoco device

    4. February 2019 at 12:13
    in reply to: Registration failed on Famoco device
    Same as Martin it is happening for us also on "standard" up-to-date smartphones.

    Right now we already saw this issue occuring on:
    - Huawei P20 Pro
    - LG K10 Power
    - Sony Xperia X
    - Samsung Galaxy S8
    - Samsung S9
    - Samsung Galaxy Xcover4

    Looking forward to the feedback.
    + 0  |  - 0

    Re: Reply To: Registration failed on Famoco device

    31. January 2019 at 10:12
    in reply to: Registration failed on Famoco device
    Today we have again another issue which seems to be somehow connected to the issue mentioned above (see below). Can you please explain also how to solve this issue or if there is an issue on your server's side?


    Caused by com.nxp.nfclib.exceptions.NxpNfcLibException: Network is not connected...
    at com.nxp.nfclib.ι.ॱ(Unknown Source:336)
    at com.nxp.nfclib.NxpNfcLib.getCardType(Unknown Source:518)
    at de.***.card.NxpNfcHelper.startListening(NxpNfcHelper.java:105)
    at de.***.ui.HomeActivity.onResume(HomeActivity.kt:103)
    at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1270)
    at android.app.Activity.performResume(Activity.java:6861)
    at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3512)
    at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3575)
    at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2817)
    at android.app.ActivityThread.-wrap12(ActivityThread.java)
    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1528)
    at android.os.Handler.dispatchMessage(Handler.java:102)
    at android.os.Looper.loop(Looper.java:154)
    at android.app.ActivityThread.main(ActivityThread.java:6316)
    at java.lang.reflect.Method.invoke(Method.java)
    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:872)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:762)

    + 0  |  - 0

    Re: Reply To: Registration failed on Famoco device

    30. January 2019 at 17:02
    in reply to: Registration failed on Famoco device
    (Just for your information: We are also using v1.2 of the TapLinx library. But my question is how to solve the issue without need for a TapLinx-Update because getting an updated version into the field needs some more time which is not acceptable for customers currently.)
    + 0  |  - 0

    Re: Reply To: Registration failed on Famoco device

    30. January 2019 at 14:51
    in reply to: Registration failed on Famoco device
    Dear TapLinx-Support,

    our customers are also facing this issue.

    Do you have some proposal what our customers then have to do to be able to not see this issue anymore? According to our research just connecting to the internet doesn't seem to work.

    Does maybe "Forcing to stop" and "Deleting the App cache" work to solve the issue for our customers?

    Thank you in advance.

    With kind regards
    Andres
    + 0  |  - 0

    Re: Reply To: TapLinx maven repository link error

    23. June 2017 at 7:52
    in reply to: TapLinx maven repository link error
    Since 22.06.2017 I also cannot access Taplinx repositories, the applications cannot be built. Please fix ASAP
    + 0  |  - 0

    Re: Reply To: Mifare DESFire EV1/2 auth/read/identify problems on Samsung Galaxy S7/S7 Edge

    29. March 2017 at 10:33
    in reply to: Mifare DESFire EV1/2 auth/read/identify problems on Samsung Galaxy S7/S7 Edge
    The problem with Samsung Galaxy S7 and Galaxy S7 Edge has been solved after the OS update to Android 7.0.
    Cards reading works correctly. So for these models it was a middleware problem. For other models that still have such problems (Samsung Grand Prime, OS 5.1.1) I will open another discussion.
    + 0  |  - 0

    Re: Reply To: Mifare DESFire EV1/2 auth/read/identify problems on Samsung Galaxy S7/S7 Edge

    3. March 2017 at 11:25
    in reply to: Mifare DESFire EV1/2 auth/read/identify problems on Samsung Galaxy S7/S7 Edge
    There is no update according to this issue from my side. I did not have any time to do further investigation. There is a new version out there (1.2), right? Should I possibly try out this first and see if the issue is solved?

    According to your comment from before:
    Our code also works fine on Nexus devices (just as for you) but does not work on Samsung Galaxy S7/S7 Edge devices. Have you tried to authenticate on an S7 or S7 Edge already?
    + 0  |  - 0

    Re: Reply To: NFC activation dialog leads to incorrect window on Samsung Galaxy S4,5,6,7

    26. January 2017 at 7:06
    in reply to: NFC activation dialog leads to incorrect window on Samsung Galaxy S4,5,6,7
    1. Initial issue has been registered in taplinx version 1.0. In that version the dialog to activate NFC lead to the incorrect settings screens on Samsung Galaxy devices family.
    2. After trying 1.1 dialog did not appear on any device I used and the app crashed when I tried to invoke library methods (Activity#onCreate -> register...). This issue was reproducible on every device I had (Huawei P9 Lite, Nexus 5, Samsung Galaxy S7/S7 Edge).
    3. In my app NFC is a must (also specified in AndroidManifest as a required feature) and only smartphones with NFC will be able to download it from PlayStore: android:name="android.hardware.nfc" android:required="true"
    Though I find the workaround you suggest with a flag very inconvenient to use. I have to check myself if NFC is off and to block all taplinx library invocations until it is activated. Could you please change the SDK so that it at least doesn't crash in such case?
    + 0  |  - 0

    Re: Reply To: Mifare DESFire EV1/2 auth/read/identify problems on Samsung Galaxy S7/S7 Edge

    19. January 2017 at 9:20
    in reply to: Mifare DESFire EV1/2 auth/read/identify problems on Samsung Galaxy S7/S7 Edge
    Updates:

    1. Changing parameters: I cache the library on internal server. SO I have to update it manually and "changing" option won't help.
    2. Tested the same code (Taplinx 1.0) on Samsung Galaxy A5. It works perfectly. So problem is very specific to Galaxy S7/S7 Edge.
    + 0  |  - 0

    Re: Reply To: Mifare DESFire EV1/2 auth/read/identify problems on Samsung Galaxy S7/S7 Edge

    17. January 2017 at 8:57
    in reply to: Mifare DESFire EV1/2 auth/read/identify problems on Samsung Galaxy S7/S7 Edge
    I have been using 1.0 Version. Tried 1.1 Today: updates:

    1. SDK causes crash when trying to register activity and NFC is off! (critical issue)
    2. Smasung Galaxy S7 recognises EV2 as UnknownCard now (doesn't work), for EV1 it stops on the first selectApplication command (see code below)
    2. Smasung Galaxy S7 recognises EV2 as UnknownCard now (doesn't work)
    3. Huawei P9 Lite (worked previously stable but now with EV1 I cannot finish a workflow I've been performing with library version 1.0).
    See the code below for details. In most cases the app stops on the last read command.

    private void readCard(Intent intent) throws Exception {
    CardType cardType = readCardType(intent);
    if (!(cardType == DESFireEV1 || cardType == DESFireEV2)) {
    cardReadFailedSubject.onNext(new CardReadFailedEvent());
    return;
    }

    IDESFireEV1 ev1 = getDesFireEV1Handler(cardType);

    ev1.getReader().connect();

    ev1.selectApplication(decodeHex(DOM_HEADER_APPLICATION_ID));

    ev1.authenticate(0x07, IDESFireEV1.AuthType.AES, KeyType.AES128, getKeyData(decodeHex(config.eidReadKey())));

    final byte[] eid = readEid(ev1);
    if (config.supportedCardTypes().contains(EID_TRANSPONDER)) {
    eidDiscoveredSubject.onNext(EidReadEvent.create(eid));
    }
    byte successorNumber;
    if (isAdminCard(eid[0]) && config.supportedCardTypes().contains(ADMIN_CARD)) {
    successorNumber = ev1.readData(10, 16, 1, IDESFireEV1.CommunicationType.Enciphered, 32)[0];
    } else {
    return;
    }

    ev1.authenticate(0x04, IDESFireEV1.AuthType.AES, KeyType.AES128, getKeyData(decodeHex(config.masterCardReadKey())));

    byte[] encrypted = ev1.readData(0x01, 0, 144, IDESFireEV1.CommunicationType.Enciphered, 144);
    ...
    }


    Please assist in fixing the issues
    + 0  |  - 0

    Re: Reply To: NFC activation dialog leads to incorrect window on Samsung Galaxy S4,5,6,7

    17. January 2017 at 8:32
    in reply to: NFC activation dialog leads to incorrect window on Samsung Galaxy S4,5,6,7
    Update in SDK Version 1.1:
    app just crashes when nfc is off when I try to register activity:

    Process: de.dom.android.garant, PID: 18858
    java.lang.RuntimeException: Unable to pause activity {de.dom.android.garant/de.dom.android.ui.HomeActivity}: com.nxp.nfclib.exceptions.NfcServiceOffException: Nfc is Off!
    at android.app.ActivityThread.performPauseActivity(ActivityThread.java:4591)
    at android.app.ActivityThread.performPauseActivity(ActivityThread.java:4550)
    at android.app.ActivityThread.handlePauseActivity(ActivityThread.java:4525)
    at android.app.ActivityThread.access$1300(ActivityThread.java:222)
    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1806)
    at android.os.Handler.dispatchMessage(Handler.java:102)
    at android.os.Looper.loop(Looper.java:158)
    at android.app.ActivityThread.main(ActivityThread.java:7229)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)
    Caused by: com.nxp.nfclib.exceptions.NfcServiceOffException: Nfc is Off!


    Is that an intentional behaviour change? SDK is not usable in such mode. Please fix ASAP (make nfc optional)
    + 0  |  - 0
Viewing 11 posts - 1 through 11 (of 11 total)