Uploading APK gives Unauthorized error

Devices \ Emulators Applications
#1

I’m trying to automatically upload an APK to the Experitest Server, as described in “Upload your Application to Your Project using cURL”, using the following shell script:

curl								\
    --location							\
    --request POST 'http://…:8080/api/v1/applications/new'	\
    --header 'Cache-Control: no-cache'				\
    --header 'Content-Type: multipart/form-data'		\
    --header 'Authorization: Basic …'				\
    --form 'file=@….apk'					\
    --form 'project=Default'

And I’m getting the following error message:

{
  "timestamp":"2020-01-31T12:30:28.764Z",
  "status":401,
  "error":"Unauthorized",
  "message":"Bad credentials",
  "path":"/api/v1/applications/new"
}

I’m pretty sure I got the correct proper authentication string as both Postman and the Obtaining Access Key function give me the same string.

Are there any caveats to know when it comes to uploading APK files?

#2

Where are you running this Rest request against?
Are you against Appium Studio agent or Seetest cloud ?

#3

Neither. We have a private cloud.

I have retried again Postman and at one point Postman changed to a shorter access string. The original access strings where about 200 character and the new one is less the 20 character.

And with that shorter key it actually works. Why this is I don’t know.

The next hurdle is the missing update function — having to work with only a new and update will be mayor pain.

#4

As far are I know its

curl -v -i -X POST -k -H "Authorization: Bearer " -F file=@C://eribank.apk https://…:8080/api/v1/applications/new

Your command shows ‘Authorization: Basic’ instead of Authorization: Bearer

#5

The video you made clearly shows to use basic authentication:

image
image.png1878×682 103 KB

See:

https://docs.experitest.com/display/TE/Native+Applications+Testing

Is the documentation outdated?

#6

Please try ‘Access Key’ (Using https://docs.experitest.com/display/TE/Obtaining+Access+Key) in Authorization header with “Bearer”.

I will check on the documentation.

#7

In the end I used my user-id and password to the upload with postman. After uploading one file with postman I used the code feature to check the used code:

image
image.png2240×1626 274 KB

It’s important the check after sending the file beause only then the Authorization filed is filled in.

#8

Great that it worked and thanks for sharing.

Let me understand, after using postman you again ran a cURL command for to query the uploaded file?

1 Like
#9

Even better I got both “Basic Auth” and “Bearer Auth” to work! :grin:

1 Like