I'm facing this error Faraday::ForbiddenError: [!] the server responded with status 403 since 2 days ago, i opened an issue on github/fastlane, firebase support, stackoverflow and till now i got no answers
https://stackoverflow.com/questions/66117989/firebase-ios-distribution-faraday-server-error-403
fastlane/fastlane#18170
can anyone help please, thanks
I'm using CirclCI, Fastlane, and Firebase App Distribution for our CD
https://stackoverflow.com/questions/66117989/firebase-ios-distribution-faraday-server-error-403
fastlane/fastlane#18170
can anyone help please, thanks
I'm using CirclCI, Fastlane, and Firebase App Distribution for our CD
Hi @abdallahnh, as the error says, it seems like the server is returning a 403 status response. 403 is standard for an unauthorised operation being carried out. Unfortunately, Faraday is simply the messenger in this case, and I don’t know why you’re getting a 403 response back or why it was working until the other day and now stopped. Those are questions for the CircleCI, Fastlane and Firebase teams, which I’m sure will be able to help.
In the meantime you could think of possibilities on why you’d receive a 403. Looking at the logs I can see you’re authenticating with a FIREBASE_TOKEN, and the authentication is successful. So the token looks OK, but maybe the account that token is bound to doesn’t have permissions to upload the IPA? That would explain a 403 error. Did you enable 2FA/MFA recently on that account maybe? Or did you, or your account administrator, made any change to permissions?
I’m sorry I can’t help you more than this, just trying to point you in the right direction while you wait for help from the other teams
In the meantime you could think of possibilities on why you’d receive a 403. Looking at the logs I can see you’re authenticating with a FIREBASE_TOKEN, and the authentication is successful. So the token looks OK, but maybe the account that token is bound to doesn’t have permissions to upload the IPA? That would explain a 403 error. Did you enable 2FA/MFA recently on that account maybe? Or did you, or your account administrator, made any change to permissions?
I’m sorry I can’t help you more than this, just trying to point you in the right direction while you wait for help from the other teams
forgive me for my newbish question but is it possible to have every Faraday call use some preset header values so that it doesn't have to be passed as an argument every single call? i have some values i need to pass in the headers for authentication and would like to set once and not worry about it. or is this a bad idea?
Hey @jmkozko, that’s far from a new bush question! It really depends on how you use Faraday. The correct way to do this would be to create one connection object with the server (API) base url and then make requests against the same connection object by providing the path and the parameters.
If you do this. Then you can provide headers to the connection as an option when you initialise it, and those will be passed to all requests performed with that connection
Here you can see an example of creating a connection object with the
headers option
Hi, How do I use faraday to run requests parallelly when there is dependency among requests? For example, consider the below scenario:
Main Dep1 Dep2
1 -> 1.1 -> 1.2
2
3 -> 3.1 -> 3.2
4 -> 4.1
You can read the above as the app wanting to make a total of 9 requests with requests under Dep1 and Dep2 depending on the response from the main request. So, request 1.2 depends on request 1.1 which in turn depends on main request 1.
Hi @satyakonidala :wave:!
Please do let me know if the above works!
Faraday::Response offers a method called on_complete, you can use that to chain dependent requests. Sorry about that lack of documentation around this but parallel requests is not a strength for any of the remaining maintainers, so we struggle a bit to provide support on this topic. We hope to revamp and improve this in the next major version though :thumbsup:Please do let me know if the above works!
Hi @scriptmonkey :wave:! The
curl example would definitely help, because I'm not sure the JSON standard allows for a "null" body, just an empty one I believe. But if you're able to make it work with curl we most probably can make it work on Faraday !
@scriptmonkey that looks to me like a simple string body with the word "null" is that it?
In that case, I believe you should be able to set that as your request body and manually set the Content-Typeheader
Faraday.post("https://api.dropboxapi.com/2/users/get_current_account", 'null', "Content-Type" => "application/json", "Authorization" => "Bearer mysupersecrettoken")Here is another example taking full advantage of Faraday tools and middleware, including those provided by the faraday_middleware gem:
require 'faraday'
require 'faraday_middleware'
base_url = 'https://api.dropboxapi.com/2'
conn = Faraday.new(base_url) do |f|
f.request :authorization, :Bearer, 'mysupersecrettoken'
f.request :json
end
conn.post('users/get_current_account', 'null')Please do let me know if this works!
P.S. the second snippet allows you to reuse the same connection (
conn) for all subsequent calls to the same API and it will automatically make the body as JSON (even if you provide a Ruby structure like a hash or array) and set your bearer token on all requests
I see that on_complete is used only with middleware but not with normal request-response. I am looking for implementations how typhoeus has on_complete (https://github.com/typhoeus/typhoeus#making-parallel-requests). Do you mind pointing me out to any available examples?
@satyakonidala yes you can also use that in your middleware if you want it to support async requests, but you can call
on_complete on any Faraday::Response object and pass a block. That block will be called as soon as the request returns and the response is saved (or immediately, if that happened already). For example, try the following (extending typhous example here, not sure which adapter you're using):conn.in_parallel do
response1 = conn.get('/first').on_complete { |response| puts response.body }
response2 = conn.get('/second').on_complete { |response| puts response.body }
puts response1.body || 'nil'
puts response2.body || 'nil'
end
I'd expect
nil to be printed twice (last 2 lines) first, and then you should see the actual bodies being printed after the requests have been completed
In your case, the on_complete blocks will trigger the next requests based on their dependencies
@satyakonidala full example (again, using typhoeus):
require 'faraday'
base_url = 'https://httpbin.org'
conn = Faraday.new(url: base_url) do |builder|
builder.request :url_encoded
# builder.response :logger
builder.adapter :typhoeus
end
conn.in_parallel do
response1 = conn.get('/anything', {test: 'test1'}).on_complete { |response| puts response.body }
response2 = conn.get('/anything', {test: 'test2'}).on_complete { |response| puts response.body }
puts response1.body || 'nil'
puts response2.body || 'nil'
end
this doesn't appear to be possible with the current implementation of in_parallel, but we think it should be if the yield at https://github.com/lostisland/faraday/blob/main/lib/faraday/connection.rb#L379 passed in the parallel manager to the block
is this a change that would likely get accepted if we submit a PR?
@scriptmonkey that’s great to hear! Thanks for the feedback!
@nohat ah I see your point, that way you can then reuse the parallel manager to enqueue the subsequent requests. Yeah that makes sense, I’ll happily review a PR that adds add. I’d just ask you to spend a little time improving the documentation around parallel requests with this new feature and with anything that you wished was there when you started working with them, you would be of great service to the Faraday community ❤️
Hi Guys. Does Faraday not work with Rails 6?
I'm facing this error NameError (uninitialized constant Faraday)
Rails version: 6.1.3.2 (using Zeitwork autoloading)
Ruby version: 2.7.3
I'm facing this error NameError (uninitialized constant Faraday)
Rails version: 6.1.3.2 (using Zeitwork autoloading)
Ruby version: 2.7.3
Faraday version: 1.4.2
1.2 version works fine
Hi! Faraday have no dependency with Rails or vice-versa, so you can use it in any Rails project. The problem with your error looks simply related to loading, possibly due to the new autoloader.
Ensure that faraday is included in your Gemfile or as a dependency of a gem in it (you can check the Gemfile.lock), and that there’s no “require: false” option on it
Ensure that faraday is included in your Gemfile or as a dependency of a gem in it (you can check the Gemfile.lock), and that there’s no “require: false” option on it
Hey Matt. It does look like it's a problem with the new autoloader. I've double checked and Faraday is included in my Gemfile and is also present in my Gemfile.lock
Again, version 1.2.0 works just fine. Any version above it seems to be facing this issue.
Again, version 1.2.0 works just fine. Any version above it seems to be facing this issue.
connection = Faraday.new(url: url, proxy: ENV['PROXY_URL']) do |faraday|
faraday.response :logger
faraday.adapter :async_http, **adapter_options
end
It doesn't seem to work for some reason
if proxy = env.request.proxy
Is this how I get the proxy from the env within an adapter?
@ioquatix that is correct, when you provide the proxy option as a simple string (that's what I assume it's in your env variable), this is automatically used to instantiate a
ProxyOptions object by the Faraday::Connection (see https://github.com/lostisland/faraday/blob/830b696ae7cbcdcaafe78deed7104e34792e5826/lib/faraday/options/proxy_options.rb#L11)
And you're also correct as of how to get the proxy, using
env.request.proxy, this should return a ProxyOptions object
However, as you can see from these tests it's sometimes a better idea to use the standard environment variables to manage proxy settings (e.g.
http_proxy). This way you won't even need to pass it to the connection, it will be picked automatically for you!