• Home
  • Line#
  • Scopes#
  • Navigate#
  • Raw
  • Download
1# NFC Error Codes
2
3> **NOTE**
4>
5> This topic describes only module-specific error codes. For details about universal error codes, see [Universal Error Codes](../errorcode-universal.md).
6
7## 3100101
8
9**Error Message**
10
11The NFC state is abnormal in the service.
12
13**Description**
14
15The NFC service fails to enable or disable NFC.
16
17**Possible Causes**
18
191. Communication with the NFC service failed.
202. The NFC chip communication is abnormal.
21
22**Solution**
23
241. Enable or disable NFC again or restart the device, and try again.
25
26## 3100201
27
28**Error Message**
29
30The tag running state is abnormal in the service.
31
32**Description**
33
34An error occurs when the NFC service executes the tag service logic.
35
36**Possible Causes**
371. The tag parameters do not match the API to invoke.
382. The NFC is disabled.
393. The tag is disconnected before the tag operation.
404. The tag chip returns an error status or response timeout.
415. Binding with the NFC service has not been established.
42
43**Solution**
441. Check whether the NFC parameters match the API to call.
452. Instruct the user to enable NFC if it is disabled.
463. Connect to the tag and then perform the read and write operations.
474. Touch and read the card again.
485. Exit the app and read the card again.
49
50## 3100202
51
52**Error Message**
53
54The element state is invalid.
55
56**Description**
57
58When the API is called, the application of the card read page is not running in the foreground.
59
60**Possible Causes**
611. The card read page is not in the foreground.
62
63**Solution**
641. The API can be called only by the page in the foreground.
65
66## 3100203
67
68**Error Message**
69
70The off() API can be called only when the on() has been called.
71
72**Description**
73
74The off() API can be called only after on() is called.
75
76**Possible Causes**
771. The foreground page of the application calls **off()** without invoking **on()**.
78
79**Solution**
801. Call **on()** first, and call **off()** before the page exits.
81
82## 3100204
83
84**Error Message**
85
86The The tag I/O operation failed.
87
88**Description**
89
90The NFC tag I/O operation fails.
91
92**Possible Causes**
931. The NFC tag does not support the read/write operation.
94
95**Solution**
961. Implement error handling and display error messages based on service scenarios.
97
98## 3100205
99
100**Error Message**
101
102The tag leaves the field.
103
104**Description**
105
106The NFC tag has been removed.
107
108**Possible Causes**
1091. The NFC tag is out of the NFC device's sensing range.
110
111**Solution**
1121. Place the NFC tag close to the NFC card reader.
113
114## 3100301
115
116**Error Message**
117
118Card emulation running state is abnormal in service.
119
120**Description**
121
122An error occurs when the NFC service executes the card emulation service logic.
123
124**Possible Causes**
1251. NFC is disabled during card emulation.
1262. The NFC chip returns an error status or response timeout.
127
128**Solution**
1291. Instruct the user to enable NFC if it is disabled.
1302. Instruct the user to disable and enable NFC to initialize the hardware again.
131
132## 3200101
133
134**Error Message**
135
136Connected NFC tag running state is abnormal in service.
137
138**Description**
139
140An error occurs when the service logic of the active NFC tag is executed.
141
142**Possible Causes**
1431. The parameter values of the active NFC tag do not match the API called.
1442. The active NFC tag chip does not respond within the specified time or returns an error status.
145
146**Solution**
1471. Check that the active NFC tag parameters match the API called.
1482. Touch and read the card again.
149