Error code 40004 android

Hi. When I launch AirDroid 4.0 app, on my Nexus 6P running Android 7.1.1, I get an error (code 4000). Message fades away and app works fine. Any idea what this error is? TIA

AirDroid Error Code: 40004question

Mon Feb 06, 2017 7:41 pm in AirDroid App

page 1 / 1

James L

Mon Feb 06, 2017 7:41 pm in AirDroid App

OP

AirDroid Error Code: 40004

Hi. When I launch AirDroid 4.0 app, on my Nexus 6P running Android 7.1.1, I get an error (code 4000). Message fades away and app works fine. Any idea what this error is? TIA

  • Reply

James L

Lillian
Admin

Wed Feb 08, 2017 6:25 am in AirDroid App

#1

Re: AirDroid Error Code: 40004

Hi. When I launch AirDroid 4.0 app, on my Nexus 6P running Android 7.1.1, I get an error (code 4000). Message fades away and app works fine. Any idea what this error is? TIA

Hi James, does the issue happen every time you open AirDroid? Can you pls send us a screenshot of that next time it appears? THX

  • Reply

Lillian
Admin

Rob

Fri Apr 21, 2017 3:37 pm in AirDroid App

#2

Re: AirDroid Error Code: 40004

I also experience it when my computer boots up and I just noticed it happens when my computer shuts down as well.

  • Reply

Rob

activekussy

Wed Dec 05, 2018 4:09 pm in AirDroid App

#3

Re: AirDroid Error Code: 40004

私のスマートフォン（XperiaZ4）でもよくこのエーラーが発します。理由は不明です。
SNSアプリの”LINE”を開いた際によく出るのでその辺りに関係しているのかもしれません。

  • Reply

activekussy

el_gallo_azul

Sun Jan 06, 2019 2:57 am in AirDroid App

#4

Re: AirDroid Error Code: 40004

I’ve been getting it on every boot of a Samsung SM-T355Y for the last couple of weeks, and never in the couple of years before that.

  • Reply

el_gallo_azul
Источник

Описание возможных ошибок в поле «code» интерфейса «ResponseWithCode»:

http code

code

Описание

200

0

Успешный запрос

400

40001

Параметры запроса неверны — не заполнены обязательные параметры/неверный формат параметров

400

40003

Приложение не найдено

400

40004

Статус приложения «inactive»

400

40005

Продукт не найден

400

40006

Статус продукта «inactive»

400

40007

Недопустимый тип продукта. Поддерживаемые типы: «consumable», «non-consumable», «subscription»

400

40008

Покупка с таким «order_id» уже существует

400

40009

У текущего клиента найдена покупка этого продукта со статусом «invoice_created». Необходимо предложить клиенту оплатить/отменить покупку

400

40010

Для типа продукта «consumable». У текущего клиента найдена покупка этого продукта со статусом «paid». Сначала требуется подтвердить потребление покупки на устройстве, а затем можно отправлять следующий запрос на покупку этого продукта

400

40011

Для типа продукта «non-consumable». У текущего клиента найдена покупка этого продукта со статусом «pre_confirmed»/«confirmed». Такой продукт уже приобретён. Более одного раза продукт не продаётся

400

40012

Для типа продукта «subscription». У текущего клиента найдена покупка этого продукта со статусом «pre_confirmed»/«confirmed». Такой продукт уже приобретён. Более одного раза продукт не продаётся

400

40013

Для типа продукта «subscription». При обращении в сервис подписок за списком продуктов «GET/products» («serviceId», «user_id») данные не были получены

400

40014

Обязательный атрибут(-ы) не пришел в запросе

400

40015

Не удалось изменить статус при обновлении покупки (переход запрещён)

400

40016

При покупке подписки непотребляемого продукта указано значение quantity > 1

400

40017

Продукт удалён, новые покупки не доступны

400

40018

Нельзя потреблять продукт с типом «тип продукта»

401

40101

Невалидный токен

401

40102

Время жизни токена истекло

403

40301

Доступ к запрашиваемому ресурсу запрещён (неавторизованно)

403

40302

Для текущего токена текущий вызов не авторизован (метод запрещён)

403

40303

Идентификатор приложения в запросе и токен не совпадают

403

40305

Неверный тип токена

404

40401

Не найдено

408

40801

Истекло время ожидания уведомления, указанное в запросе

500

50***

Внутренняя ошибка платежного сервиса
Источник

Describe the bug

ksqlDB java client giving error while executing pull/push queries at ‘/query-stream’ api endpoint.

Error: Received 400 response from server: This endpoint is only available when using HTTP2. Error code: 40004

Also tried through CURL command, hitting with same error

Command:

curl -X "POST" "https://ksql.k8s.com:443/query-stream" --http2 -H "Content-Type: application/json; charset=utf-8" -d $'{ "sql": "SELECT * FROM EVENTS EMIT CHANGES;", "streamsProperties": {"ksql.streams.auto.offset.reset": "earliest"} }' | jq .

CURL output :

{
  "@type": "generic_error",
  "error_code": 40004,
  "message": "This endpoint is only available when using HTTP2"
}

To Reproduce

Steps to reproduce the behavior, include:

  1. The version of KSQL: 0.12.0
  2. JDK: Zulu 11
  3. Sample source data:
public class KSQLClient {
    protected static final Logger log = LoggerFactory.getLogger(KSQLClient.class);

    public static void main(String[] args) throws ExecutionException, InterruptedException, MalformedURLException, URISyntaxException {
        URI uri = new URL("https://ksql-server:443/").toURI();
        ClientOptions options = ClientOptions.create()
                .setHost(uri.getHost())
                .setPort(uri.getPort())
                .setUseTls(true)
                .setUseAlpn(true)
                .setVerifyHost(false);

        Vertx vertx = Vertx.vertx().exceptionHandler((t) -> {
            log.error("Unhandled exception in Vert.x", t);
        });
        vertx.exceptionHandler(t -> System.out.println("Unhandled exception in Vert.x" + t));

        Client client = Client.create(options, vertx);
        Map<String, Object> properties = Collections.singletonMap("auto.offset.reset", "earliest");
        StreamedQueryResult streamedQueryResult = client.streamQuery(
                "SELECT * FROM EVENTS EMIT CHANGES;", properties).get();
        for (int i = 0; i < 10; i++) {
            Row row = streamedQueryResult.poll();
            if (row != null) {
                System.out.println("Received a row!");
                System.out.println("Row: " + row.values());
            } else {
                System.out.println("Query has ended.");
            }
        }
        vertx.close();
        client.close();
    }
}

Expected behavior

‘/query-stream’ api endpoint should return the query result stream data.

However push/pull queries are working as expected through ksqldb-cli client.

Источник

Error code

Instructions

Investigation hint

4000

resources not found, if you use aab please call PAGConfig.setPackageName

If you use obfuscation, please make sure add Pangle’s resource to whitelist, you can refer to this link: link

And if you use Pangle’s AAB function, please call PAGConfig.setPackageName, and use .to split the base package name and module package name.

10000

Please exec TTAdSdk.init before load ad

Initialize the sdk and then initiate an ad request

10002

load time out

The ad object is not successfully returned within the specified time, and it is not recommended to initiate the request again.

10003

resource error

Resource loading failed due to network and other reasons.

20001

No fill

40001

BadRequest: Http request pb error

Indicates that some necessary parameters have invalid values. Please check the integration guideline on Pangle platform

40004

BadRequest: Empty Slot ID

Indicates that the slotID is null

40005

BadRequest: Invalid Ad Size

Indicates that the AdSize is missing or an unsupported size is passed.

40006

Invalid Slot ID

Indicates that the length of the slotID is incorrect, or an empty string is passed.

40007

BadRequest: Ad counts error

Indicates that the Ad counts is invalid

40008

BadRequest: Image size error

Indicates that the image size is not supported.

40009

Invalid App ID

Indicates that the app id is invalid or app id is missing

40013

Using App Open Ad’s placement to other request method.

The non-splash ad request method uses the splash ad placement ID. Check whether the ad placement ID used for the requested advertisement is correct, the app open ad ad placement ID is a nine-digit number starting with 8

40016

BadRequest: Slot ID and App ID is not matched

Indicates that the relationship between App Id and Slot Id is invalid or App Id is missing.

40018

Invalid Package Name

Indicates that the package name of your project does not match the package name you filled in Pangle platform.

40019

BadRequest: Ad Type and Slot Id is not matched

Indicates that Ad Type and Slot Id is not matched. For example, try to load a rewarded ad with a banner ad slot id.

40021

BadRequest: Invalid SHA1 value

Indicates that the SHA1 is not matched with the SHA1 you entered on the Pangle platform

40022

BadRequest: Incorrect API method

Indicates that the API method is incorrect

40024

BadRequest: The SDK version is too low

Please update to the latest SDK

40025

BadRequest: verification failed

Update to the latest SDK

40029

BadRequest: Incorrect API method

There are three situations: One: IOS: ad request method error, SDK rendering advertisement and self rendering ad request method are different. Solution: Use the SDK rendering method and the correct parameters to request SDK rendering ad. Two: The server slotID configuration is not effective: you need to wait 2-3 minutes for the new slotID to request the ad. Three: Low SDK version: the SDK version used is too low (lower than 2.9.5.0) and does not support personalized SDK rendering function. Solution: update to the latest version of the Platform SDK.

40034

Incorrect Bidding Ad Placement

1. Bidding ad placement can not be used in non-bidding environment 2. Non-bidding ad placement can not be used in bidding environment.

50001

Servers error

Server error, if the error could be 100% replicated, please give feedback to us via pangle_support@bytedance.com

-1

Data parsing failed.

For the collection of client code problems, you can first check the following situations: One: show is called in the child thread. Two: ViewGroup is empty when registering click events. Three: The business logic of the media in the onFeedLoaded callback is abnormal, which causes the SDK to go to the onError callback. If the above ideas still can not solve your problem, you can contact the TS

-2

Network error

Indicates that your network connection is not stable enough.

-16

Prohibit requesting ads

Pangle don’t have Children ads, you can not get fill when coppa = 1

101

Data parsing failed for template ads

Please update to the latest sdk.

102

Template missing

Please update to the latest sdk.

103

Subtemplate missing

Please update to the latest sdk.

107

SDK rendering timeout

Please update to the latest sdk.

108

SDK rendering timeout

Please update to the latest sdk.

109

Template loads failed

Please update to the latest sdk.

113

Dynamic-Native 1.0 JS parsing error

Re-request ads

117

Dynamic-Native 1.0 JS parsing timeout

Re-request ads

118

Dynamic-Native 1.0 rendering error

Re-request ads

123

Dynamic-Native 2.0 SDK parsing error

Re-request ads

127

Dynamic-Native 2.0 SDK parsing timeout

Re-request ads

128

Dynamic-Native 2.0 SDK rendering error

Re-request ads

601

Link establishment failed

Check network status and request ads again

602

Link establishment timeout

Check network status and request ads again

603

Ads returned abnormally

Re-request ads

604

Ads parsing failed

Re-request ads

605

Ads parsing failed

Re-request ads

606

Ads parsing abnormally

Re-request ads

607

Ads read and write failed

Re-request ads

608

Ads read and write failed

Re-request ads

609

Ads download failed

Re-request ads

610

Ads download abnormally

Re-request ads

611

Ads request cancelled

Re-request ads

612

Image load abnormally

Re-request ads
Источник

Понравилась статья? Поделить с друзьями:

Читайте также:

  • Error 7014 invalid dbf table
  • Error code 3008
  • Error 701 bolyguard
  • Error code 3006
  • Error 701 0 фотоловушка

    • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии