No able to get coverage on newly created shapefile

[earthdaily]

No able to get coverage on newly created shapefile

[myarjunar]

Hi @vincentlel , I'm sorry but I can't replicate it. using the same workflow, the plugin successfully retrieve the coverage results as follow;

could you try it again? I'm afraid it was only a connection or server error.

[vincentlel]

Hi Rohmat, I am still having the same error on my side. Vincent Le ven. 26 avr. 2019 à 10:31, Muhammad Yarjuna Rohmat < [email protected]> a écrit :

…

Hi @vincentlel <https://github.com/VincentLel> , I'm sorry but I can't replicate it. using the same workflow, the plugin successfully retrieve the coverage results as follow; [image: Screen Shot 2019-04-26 at 22 03 10] <https://user-images.githubusercontent.com/11134669/56818828-ad072d80-6872-11e9-8f29-9d1d0137c16e.png> could you try it again? I'm afraid it was only a connection or server error. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#76 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALVUDNQ6WE5V56665VNLSHLPSMN5FANCNFSM4HH5V2RQ> .

[vincentlel]

Hi Rohmat, As I made several edit on this testing shapefile I am just sharing the latest version. Vincent Le ven. 26 avr. 2019 à 10:31, Muhammad Yarjuna Rohmat < [email protected]> a écrit :

…

Hi @vincentlel <https://github.com/VincentLel> , I'm sorry but I can't replicate it. using the same workflow, the plugin successfully retrieve the coverage results as follow; [image: Screen Shot 2019-04-26 at 22 03 10] <https://user-images.githubusercontent.com/11134669/56818828-ad072d80-6872-11e9-8f29-9d1d0137c16e.png> could you try it again? I'm afraid it was only a connection or server error. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#76 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALVUDNQ6WE5V56665VNLSHLPSMN5FANCNFSM4HH5V2RQ> .

[myarjunar]

@vincentlel I finally can replicate the issue. Referring to https://docs.google.com/document/d/1CY2kVjnGSFClpC8rZ2uIa6nk5XaQaJIXZrBSEVxkDPA/edit, when I was testing it using staging credentials, it's working perfectly. But the issue happens when I made the request using production credentials, the API response is as follow:

{
    "errors": {
        "body": {
            "": [
                {
                    "code": "forbidden",
                    "message": "You can't create Farm for this grower 'n5v63mw'"
                }
            ]
        }
    },
    "code": "model_validation_error",
    "message": "Bad request: see the Errors field for details"
}

We need to handle every error response from Bridge API although it's quite hard for me since there is no strict error response format and no clear documentation stating about all possible error responses. At least I will first handle this error response first.

[vincentlel]

thanks for the investigation, I have enough to dig into it on my side. I will take care of this.

…

__________________________________ Vincent LELANDAIS 800 Foxberry Circle Hamel, MN 55340 USA Email : [email protected] Cell: [phone] Cell: [phone] Le ven. 26 avr. 2019 à 11:49, Muhammad Yarjuna Rohmat < [email protected]> a écrit :

@vincentlel <https://github.com/VincentLel> I finally can replicate the issue. Referring to https://docs.google.com/document/d/1CY2kVjnGSFClpC8rZ2uIa6nk5XaQaJIXZrBSEVxkDPA/edit, when I was testing it using staging credentials, it's working perfectly. But the issue happens when I made the request using production credentials, the API response is as follow: { "errors": { "body": { "": [ { "code": "forbidden", "message": "You can't create Farm for this grower 'n5v63mw'" } ] } }, "code": "model_validation_error", "message": "Bad request: see the Errors field for details" } We need to handle every error response from Bridge API although it's quite hard for me since there is no strict error response format and no clear documentation stating about all possible error responses. At least I will first handle this error response first. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#76 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALVUDNSIAUOIZOCBKLFBWU3PSMXBDANCNFSM4HH5V2RQ> .