I guess I’ll just have to dig in deeper when I hav...
# general
e
I guess I’ll just have to dig in deeper when I have some time, but a clean solidus instance + easypost is causing an error
g
Silly question, but you did set easypost as the shipping estimator in spree.rb, right? And you grabbed your api key and added it to the easypost config? I just went through installing that on my local for testing and went through some troubleshooting of my own.
e
@Given Reed yes, I did, if you’re referring to this:
Copy code
# config/initializers/spree.rb
Spree.config do |config|
  config.stock.estimator_class = 'SolidusEasypost::Estimator'
end
in truth, I had expected the solidus ecosystem to be a lot more fleshed out than it actually is
so we’ve started looking at alternate ecosystems, since Solidus has proven to be a bit anemic in some key areas
g
It's not going to be a match for everybody, that's true.
Did you also set the API key for the easypost account?
e
yes, I tried both the development and production key
I don’t mind digging into things, but when you’re using libraries that have essentially zero error reporting, it makes even the smallest issue a potential rabbit hole
g
Yep, I totally get it. I spent multiple days tracking down some issues I was having with the easypost gem that were all because I had added a second USPS carrier and was duplicating the results that were coming back.
e
I don’t know why I’m telling you all this, I’m just venting
one dev to another lol
g
lol, no worries, sometimes that's all you need 😛
it's mostly just that I just went through some easypost stuff and it was something silly that I overlooked, so I was hoping that yours was a similar thing