nfc_t4t_done() is returning NRF_ERROR_INVALID_STATE. Docs says it always returns NRF_SUCCESShttps://devzone.nordicsemi.com/f/nordic-q-a/19288/nfc_t4t_done-is-returning-nrf_error_invalid_state-docs-says-it-always-returns-nrf_successI&#39;ve been working on a separate problem with the NFC Type 4 library when I ran across this. I can duplicate it in the experimental_writeable_ndef_msg example. All I did was add err_code = nfc_t4t_done();&quot; right before the while(1) loop in main() .en-USTelligent Community 13Mon, 30 Jan 2017 08:19:37 GMTRE: nfc_t4t_done() is returning NRF_ERROR_INVALID_STATE. Docs says it always returns NRF_SUCCESShttps://devzone.nordicsemi.com/thread/74765?ContentTypeID=1Mon, 30 Jan 2017 08:19:37 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d7801552-446f-45aa-913b-a58dbb41e8feFormerMember<p>Thanks for reporting this, I have reported the missing documentation internally.</p><div style="clear:both;"></div>RE: nfc_t4t_done() is returning NRF_ERROR_INVALID_STATE. Docs says it always returns NRF_SUCCESShttps://devzone.nordicsemi.com/thread/74764?ContentTypeID=1Sat, 28 Jan 2017 11:04:27 GMT137ad170-7792-4731-bb38-c0d22fbe4515:081d3bb9-e6d9-40eb-a63e-423dd83b88e9Daniel Wang<p>You need to call <code>nfc_t4t_emulation_stop()</code> before you call <code>nfc_t4t_done()</code>. I guess the documentation needs to be updated with &quot;<code>NRF_ERROR_INVALID_STATE</code>: If emulation is in running state.&quot;</p><div style="clear:both;"></div>