Android build and deployoment started failing

Once again, without any changes in our travis.yml, our builds started failing for our Android app. We we’re able to fix the build issues, but now we are stuck with failing deployment.

Super frustrating as there is no useful help from the customer support team and our app release is pending on this.

Does anyone have a clue here how to fix this? Thanks!


dpl_0

8737$ rvm use $(travis_internal_ruby) --fuzzy do ruby -S gem uninstall -aIx dpl

8773/home/travis/.rvm/gems/ruby-3.3.5/gems/cl-1.2.4/lib/cl/opts.rb:112:in block in taint': undefined method taint’ for an instance of String (NoMethodError)

8774

8775 [key, self[key] && self[key].secret? ? value.taint : value]

8776 ^^^^^^

8777 from /home/travis/.rvm/gems/ruby-3.3.5/gems/cl-1.2.4/lib/cl/opts.rb:111:in `each’

8778 from /home/travis/.rvm/gems/ruby-3.3.5/gems/cl-1.2.4/lib/cl/opts.rb:111:in `map’

8779 from /home/travis/.rvm/gems/ruby-3.3.5/gems/cl-1.2.4/lib/cl/opts.rb:111:in `taint’

8780 from /home/travis/.rvm/gems/ruby-3.3.5/gems/cl-1.2.4/lib/cl/opts.rb:25:in `apply’

8781 from /home/travis/.rvm/gems/ruby-3.3.5/gems/cl-1.2.4/lib/cl/cmd.rb:62:in `initialize’

8782 from /home/travis/.rvm/gems/ruby-3.3.5/gems/dpl-2.0.3.beta.4/lib/dpl/provider.rb:196:in `initialize’

8783 from /home/travis/.rvm/gems/ruby-3.3.5/gems/cl-1.2.4/lib/cl/runner/default.rb:32:in `new’

8784 from /home/travis/.rvm/gems/ruby-3.3.5/gems/cl-1.2.4/lib/cl/runner/default.rb:32:in `cmd’

8785 from /home/travis/.rvm/gems/ruby-3.3.5/gems/cl-1.2.4/lib/cl/runner/default.rb:26:in `run’

8786 from /home/travis/.rvm/gems/ruby-3.3.5/gems/cl-1.2.4/lib/cl.rb:34:in `run’

8787 from /home/travis/.rvm/gems/ruby-3.3.5/gems/dpl-2.0.3.beta.4/lib/dpl/cli.rb:11:in `run’

8788 from /home/travis/.rvm/gems/ruby-3.3.5/gems/dpl-2.0.3.beta.4/bin/dpl:9:in `<top (required)>’

8789 from /home/travis/.rvm/gems/ruby-3.3.5/bin/dpl:25:in `load’

8790 from /home/travis/.rvm/gems/ruby-3.3.5/bin/dpl:25:in `’

8791failed to deploy

Have you tried adding edge: true into your .travis.yml?

1 Like

This solved the issue. Added it below deploy: