Forum Replies Created

  • Re: Reply To: TapLinx is not compatible with Firebase Push

    16. January 2017 at 13:07
    in reply to: TapLinx is not compatible with Firebase Push
    Could you provide some ETA? I'm waiting on this, it has been 10 days already.
    + 0  |  - 0

    Re: Reply To: TapLinx is not compatible with Firebase Push

    11. January 2017 at 14:45
    in reply to: TapLinx is not compatible with Firebase Push
    We are using

    compile('taplinx-android:nxpnfcandroidlib:1.1@aar') { transitive = true }

    It still fails when firebase is added because of conflict.
    + 0  |  - 0

    Re: Reply To: Switching MiFare Plus to S3

    10. January 2017 at 17:54
    in reply to: Switching MiFare Plus to S3
    How to update?
    + 0  |  - 0

    Re: Reply To: Switching MiFare Plus to S3

    7. January 2017 at 12:07
    in reply to: Switching MiFare Plus to S3
    Any news here? I'm still waiting for this...
    + 0  |  - 0

    Re: Reply To: Switching MiFare Plus to S3

    14. November 2016 at 15:06
    in reply to: Switching MiFare Plus to S3
    Any news on this? This is critical to our setup.
    + 0  |  - 0

    Re: Reply To: Switching MiFare Plus to S3

    11. October 2016 at 23:22
    in reply to: Switching MiFare Plus to S3
    Hello,

    I have the same exact problem reported here.


    byte[] key = new byte[16]{0x4b, 0x2c, 0xf0, 0xbb, 0x69, 0x5e, 0xb4, 0xdd, 0x80, 0x42, 0xd4, 0x24, 0x64, 0x71, 0x5e, 0x5c};
    KeyData keyData = new KeyData();
    keyData.setKey(new SecretKeySpec(key, "AES"));

    // later on, when a card detection intent is received:
    IPlusEV1SL1 card = PlusSL1Factory.getInstance().getPlusEV1SL1(mifare.getCustomModules());
    card.switchToSL3(keyData);


    This fails with
    com.nxp.nfclib.exceptions.SecurityException: error:1e06b06a:Cipher functions:EVP_DecryptFinal_ex:DATA_NOT_MULTIPLE_OF_BLOCK_LENGTH


    But my key clearly has exactly 16 bytes. I'm using TapLinx 1.0. What is wrong here?
    + 0  |  - 0
Viewing 6 posts - 1 through 6 (of 6 total)