Failed unmarshal json content of the inline environment variables: json: cannot unmarshal number into Go value of type string

#1

Bitrise Build Issue Report template

Description of the issue

There is a branch develop in our project that is built daily. For quite a few days, there is no change in that branch. It was building successfully until today. Today we face this error “Failed unmarshal json content of the inline environment variables: json: cannot unmarshal number into Go value of type string” while building any branch. I can assure you there is no change in config or yml or develop branch

Environment:

test environment

If on Bitrise.io: which stack? If not on Bitrise.io: on what operating system? (Plus any other information you can share)

Standard Machine 2CPU(n1) 7.5 GB Ram macos 2CPU(Intel Xeon 75570)/ 4GB RAM

Reproducibility

  • Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : NO
  • Does a rebuild without caches help? (You can remove the Cache:Pull and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app. : NO
  • Does the issue happen sporadically, or every time? :Every Time
  • Does upgrading the build Step to the latest version help? : NO
  • When did the issue start? : Today

Local reproduction

Can it be reproduced on your own Mac/PC by following our local debug guide? Please follow at least the first section (“Testing with a full clean git clone”) to make sure to test the state of the code what bitrise.io will get when it does a git clone in the clean environment! If possible please note which sections you tried.

NO

Build log

Please copy paste the build’s bitrise.io URL here (or if the issue happens somewhere else then the full logs), or if you can’t share the url / log here then send the url or full log through a private channel (e.g. email - https://www.bitrise.io/contact ), with a link to the related Discuss issue.

0 Likes

#2

Hi @HabibAliAtFolio3!

As discussed on Intercom as well, the issue has been resolved, thanks for your patience!

0 Likes

closed #3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

0 Likes