• Home
  • Line#
  • Scopes#
  • Navigate#
  • Raw
  • Download
1# Window 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## 1300001 Repeated Operation
8**Error Message**
9
10Repeated operation.
11
12**Description**
13
14This error code is reported when a repeated operation is performed.
15
16**Possible Causes**
171. The window has been created.
182. The window is in the current state.
19
20**Solution**
21
22Before creating a window, check whether the window has been created or is in the current state.
23
24## 1300002 Abnormal Window State
25**Error Message**
26
27This window state is abnormal.
28
29**Description**
30
31This error code is reported when you operate a window in an abnormal state, for example, a window that is not created yet or has been destroyed.
32
33**Possible Causes**
34
35The window to operate is not created or has been destroyed.
36
37**Solution**
38
39Operate the window that exists.
40
41## 1300003 Abnormal Window Manager Service
42**Error Message**
43
44This window manager service works abnormally.
45
46**Description**
47
48This error code is reported when the window manager service is abnormal.
49
50**Possible Causes**
51
52The internal services of the window are not started normally.
53
54**Solution**
55
56Try again later or restart the device.
57
58## 1300004 Unauthorized Operation
59**Error Message**
60
61Unauthorized operation.
62
63**Description**
64
65This error code is reported when the API does not have the required permissions to operate an object.
66
67**Possible Causes**
68
69The window object of another process is operated.
70
71**Solution**
72
73Check whether unauthorized operations are performed on the object of another process. If yes, delete the operations.
74
75## 1300005 Abnormal Window Stage
76**Error Message**
77
78This window stage is abnormal.
79
80**Description**
81
82This error code is reported when you operate a WindowStage in the abnormal state, for example, a WindowStage that has been destroyed.
83
84**Possible Causes**
85
86The WindowStage is not created or has been destroyed.
87
88**Solution**
89
90Before operating a WindowStage, check whether it exists.
91
92## 1300006 Abnormal Window Context
93**Error Message**
94
95This window context is abnormal.
96
97**Description**
98
99This error code is reported when you operate a window context in the abnormal state, for example, a window context that has been destroyed.
100
101**Possible Causes**
102
103The window context has been destroyed when being operated.
104
105**Solution**
106
107Before operating the window context, check whether it exists.
108
109## 1300007 Application Startup Failure by WindowExtensionAbility
110
111**Error Message**
112
113Failed to start the ability.
114
115**Description**
116
117This error code is reported when a WindowExtensionAbility fails to start an application.
118
119**Possible Causes**
120
121Incorrect parameters are passed into the API used by the WindowExtensionAbility to start the application.
122
123**Solution**
124
125Pass in the correct parameters.
126
127## 1300008 Display Device Exception
128
129**Error Message**
130
131The display device is abnormal.
132
133**Description**
134
135This error code is reported when the display device is abnormal.
136
137**Possible Causes**
138
1391. The display device is not ready.
1402. The display device is removed.
1413. The display device is damaged.
142
143**Solution**
144
145Ensure that the display device is normal.
146
147## 1300009 Invalid Parent Window
148
149**Error Message**
150
151The parent window is invalid.
152
153**Description**
154
155This error code is reported when the parent window is invalid.
156
157**Possible Causes**
158
1591. No parent window is bound.
1602. The parent window bound is abnormal. For example, the parent window has been destroyed.
161
162**Solution**
163
1641. Ensure that the subwindow is bound to the parent window.
1652. Ensure that the status of the parent window is normal.
166
167## 1300010 Unsupported Operation in the Current Window Mode
168
169**Error Message**
170
171The operation in the current window status is invalid.
172
173**Description**
174
175This error code is reported when the operation is not supported in the current window mode.
176
177**Possible Causes**
178
1791. Perform the move operation in the full-screen or split-screen window.
1802. Perform the resize operation in the full-screen or split-screen window.
181
182**Solution**
183
1841. Do not move the full-screen or split-screen window.
1852. Do not resize the full-screen or split-screen window.
186
187## 1300011 Failure in Destroying a PiP Window
188
189**Error Message**
190
191Failed to destroy the PiP window.
192
193**Description**
194
195This error code is reported when destroying a PiP window fails.
196
197**Possible Causes**
198
199The pointer to the PiP window is null.
200
201**Solution**
202
203No action is required.
204
205## 1300012 Abnormal PiP Window Status
206
207**Error Message**
208
209The PiP window state is abnormal.
210
211**Description**
212
213This error code is reported when the PiP window status is abnormal.
214
215**Possible Causes**
216
217The PiP window status is abnormal.
218
219**Solution**
220
221No action is required.
222
223## 1300013 Failure in Creating a PiP Window
224
225**Error Message**
226
227Failed to create the PiP window.
228
229**Description**
230
231This error code is reported when creating a PiP window fails.
232
233**Possible Causes**
234
2351. Incorrect parameters are passed in to create the PiP window.
2362. Attempt to start PiP in a non-full-screen window.
237
238**Solution**
239
2401. Correct the input parameters.
2412. Do not start PiP in a non-full-screen window.
242
243## 1300014 PiP Internal Error
244
245**Error Message**
246
247PiP internal error.
248
249**Description**
250
251This error code is reported when an internal error occurs in PiP.
252
253**Possible Causes**
2541. The window on which the PiP feature depends is abnormal or empty.
2552. The PiP controller is abnormal.
256
257**Solution**
258
259No action is required.
260
261## 1300015 Repeated PiP Operations
262
263**Error Message**
264
265Repeated PiP operation.
266
267**Description**
268
269This error code is reported when a repeated PiP operation is performed.
270
271**Possible Causes**
272
273The PiP window has been started or closed.
274
275**Solution**
276
277Do not start or stop PiP repeatedly.
278
279## 1300016 Parameter Verification Error
280
281**Error Message**
282
283Parameter validation error.
284
285**Description**
286
287This error code is reported when parameters are incorrect. For example, the parameter value exceeds the allowed range, the length of the string or array does not meet the requirements, or the parameter format is incorrect.
288
289**Possible Causes**
290
2911. The parameter value is out of range.
292
2932. The parameter length exceeds the allowed limits.
294
2953. The parameter format is incorrect.
296
297**Solution**
298
299Verify that the parameters adhere to the required standards.
300
301## 1300017 Filter Controller Calling Error
302
303**Error Message**
304
305Incorrect filter calling.
306
307**Description**
308
309This error code is reported when the filter controller is invalidly invoked. For example, the invoking sequence is incorrect.
310
311**Possible Causes**
312
313**setBackgroundFilter** is called after **animateBackgroungFilter**.
314
315**Solution**
316
317Check the order of operations to ensure that **setBackgroundFilter** is called before **animateBackgroungFilter**.
318
319## 1300018 API Call Timeout
320
321**Error Message**
322
323API call timed out.
324
325**Description**
326
327This error code is reported when the API call times out.
328
329**Possible Causes**
330
331The wait time for a synchronous API call exceeds the upper limit.
332
333**Solution**
334
335The solution will vary based on the specific context. Typical approaches are:
336
3371. Retry the API call a limited number of times.
338
3392. Implement fallback measures, such as using cached data or alternative logic.
340
3413. Abort the current processing logic.
342
343## 1300019 Floating Ball Parameter Verification Error
344
345**Error Message**
346
347Wrong parameters for operating the floating ball.
348
349**Description**
350
351This error code is reported when parameters are incorrect. For example, the parameter value exceeds the allowed range, the length of the string or array does not meet the requirements, or the parameter format is incorrect.
352
353**Possible Causes**
354
3551. The parameter value is out of range.
356
3572. The parameter length exceeds the allowed limits.
358
3593. The parameter format is incorrect.
360
361**Solution**
362
3631. Ensure that the parameter value is within the allowed range.
364
3652. Ensure that the parameter length is within the allowed limits.
366
3673. Use the correct format for parameters.
368
369## 1300020 Failure in Creating a Floating Ball Window
370
371**Error Message**
372
373Failed to create the floating ball window.
374
375**Description**
376
377This error code is reported when creating a floating ball window fails.
378
379**Possible Causes**
380
3811. Incorrect parameters are passed in to start the floating ball.
382
3832. Attempt to start the floating ball on an unsupported device.
384
3853. Attempt to start the floating ball when the application is in the background.
386
387**Solution**
388
3891. Check the parameters before starting the floating ball.
390
3912. Verify that the device supports the floating ball before starting it.
392
3933. Ensure that the application is in the foreground before starting the floating ball.
394
395## 1300021 Failure in Starting Multiple Floating Balls
396
397**Error Message**
398
399Failed to start multiple floating ball windows.
400
401**Description**
402
403This error code is reported when starting multiple floating balls fails.
404
405**Possible Causes**
406
407Multiple floating ball controllers are created for the same application.
408
409**Solution**
410
411An application should create only one floating ball controller to start the floating ball. You are advised to use a singleton pattern to hold the floating ball controller.
412
413## 1300022 Repeated Floating Ball Operation
414
415**Error Message**
416
417Repeated floating ball operation.
418
419**Description**
420
421This error code is reported when a repeated operation is performed on the floating ball.
422
423**Possible Causes**
424
4251. Attempt to start the floating ball while it is already running.
426
4272. Attempt to stop the floating ball after it has already stopped.
428
4293. Attempt to register the floating ball callback multiple times.
430
431**Solution**
432
4331. Check whether the floating ball is already running before starting it.
434
4352. Check whether the floating ball has already stopped before stopping it.
436
4373. Ensure that the callback is not already registered before registering the floating ball callback.
438
439## 1300023 Internal Error of the Floating Ball
440
441**Error Message**
442
443Floating ball internal error.
444
445**Description**
446
447This error code is reported when an internal error occurs in the floating ball.
448
449**Possible Causes**
450
4511. The window on which the floating ball depends is abnormal or empty.
452
4532. The floating ball controller is abnormal or empty.
454
455**Solution**
456
4571. Check the window of the floating ball to ensure it is not empty.
458
4592. Check the status of the floating ball controller to ensure it is not empty.
460
461## 1300024 Abnormal Floating Ball Window State
462
463**Error Message**
464
465The floating ball window state is abnormal.
466
467**Description**
468
469This error code is reported when the floating ball window state is abnormal.
470
471**Possible Causes**
472
473The floating ball window may not have been created or may have been destroyed.
474
475**Solution**
476
477Check that the floating ball window has been created and is not destroyed.
478
479## 1300025 Unsupported Operation in the Current Floating Ball State
480
481**Error Message**
482
483The floating ball state does not support this operation.
484
485**Description**
486
487This error code is reported when the operation is not supported in the current floating ball state.
488
489**Possible Causes**
490
4911. Attempt to update the floating ball when it is not active.
492
4932. Attempt to query window information when the floating ball is not active.
494
4953. Attempt to launch an application window when the floating ball is not active.
496
4974. Attempt to start the floating ball before the stop process is complete.
498
499**Solution**
500
5011. Check whether the floating ball is active before updating it.
502
5032. Check whether the floating ball is active before querying window information.
504
5053. Check whether the floating ball is active before launching an application window.
506
5074. Wait for the floating ball to stop completely before restarting it.
508
509## 1300026 Failure in Launch an Application Window via a Floating Ball
510
511**Error Message**
512
513Failed to restore the main window.
514
515**Description**
516
517This error code is reported when launching an application window via the floating ball fails.
518
519**Possible Causes**
520
5211. Incorrect parameters are passed.
522
5232. The application window is not launched within 5 seconds after clicking.
524
5253. Attempt to launch a window that belongs to another application.
526
527**Solution**
528
5291. Check the parameters used to launch the application window.
530
5312. Ensure to launch the application window within 5 seconds after clicking.
532
5333. Launch the window that belongs to the current application.
534
535## 1300027 Cannot Change Template Type When Updating the Floating Ball
536
537**Error Message**
538
539When updating the floating ball, the template type cannot be changed.
540
541**Description**
542
543This error code is reported when changing the template type fails.
544
545**Possible Causes**
546
547The template type used during the update is inconsistent with the one used during creation.
548
549**Solution**
550
551Ensure that the template type used when updating the floating ball matches the one used when it was created.
552
553## 1300028 Floating Ball Based on a Static Template Cannot Be Updated
554
555**Error Message**
556
557Updating static template-based floating balls is not supported.
558
559**Description**
560
561This error code is reported when users attempt to update a floating ball based on a static template.
562
563**Possible Causes**
564
565Updating floating balls based on static templates is not supported.
566
567**Solution**
568
569Delete any existing floating balls based on static templates and create new ones.
570
571## 1001 Window Null Pointer Exception<sup>(deprecated)</sup>
572**Error Message**
573
574A window null pointer occurs.
575
576**Description**
577
578This error code is reported when you operate a window pointed to by a null pointer.
579
580**Possible Causes**
581
582A null pointer is used.
583
584**Solution**
585
586Operate the window that exists.
587
588## 1002 Invalid Window Type<sup>(deprecated)</sup>
589**Error Message**
590
591This window type is invalid.
592
593**Description**
594
595This error code is reported when the window type is invalid.
596
597**Possible Causes**
598
599An invalid window type is used. For details about valid window types, see [WindowType](arkts-apis-window-e.md#windowtype7).
600
601**Solution**
602
603Use a window type supported.
604
605## 1003 Invalid Window Parameter<sup>(deprecated)</sup>
606**Error Message**
607
608This window parameter is invalid.
609
610**Description**
611
612This error code is reported when a window parameter is invalid.
613
614**Possible Causes**
615
616Invalid parameters are passed in.
617
618**Solution**
619
620Correct the parameters.
621
622## 1004 Ability Service Exception<sup>(deprecated)</sup>
623**Error Message**
624
625This system ability service works abnormally.
626
627**Description**
628
629This error code is reported when the ability service is abnormal.
630
631**Possible Causes**
632
633When the window is destroyed, the proxy fails to be initialized.
634
635**Solution**
636
637Restart the device and try again.
638
639## 1005 IPC Failure<sup>(deprecated)</sup>
640**Error Message**
641
642This window IPC failed.
643
644**Description**
645
646This error code is reported when IPC fails.
647
648**Possible Causes**
649
650The window parameters fail to be transferred.
651
652**Solution**
653
654Before operating a window, ensure that the client and server services in the window are normal.
655
656## 1007 Application Startup Failure by WindowExtensionAbility<sup>(deprecated)</sup>
657**Error Message**
658
659Failed to start the ability.
660
661**Description**
662
663This error code is reported when a WindowExtensionAbility fails to start an application.
664
665**Possible Causes**
666
667Incorrect parameters are passed into the API used by the WindowExtensionAbility to start the application.
668
669**Solution**
670
671Pass in the correct parameters.
672