Error-Response not useful for non-valid subscription addon.

[azngeek]

Lets assume that you have a plan with fixed add-ons and you try to add an add-on which is not defined in the plan.

This might be the xml with the invalid addon

xml
<?xml version="1.0"?>
<purchase>
	<account>
		<account_code>100067545</account_code>
		<first_name>Test</first_name>
		<last_name>User</last_name>
		<email>t@test.de</email>
		<billing_info>
			<token_id>qQYe28t1xDzHqAQy9IDI0Q</token_id>
		</billing_info>
		<address>
			<address1>Klaus-Dieter-Eckert-Platz 558</address1>
			<city>Rees</city>
			<zip>48555</zip>
			<country>DE</country>
		</address>
	</account>
	<adjustments/>
	<collection_method>automatic</collection_method>
	<currency>EUR</currency>
	<subscriptions>
		<subscription>
			<plan_code>1</plan_code>
			<unit_amount_in_cents>0</unit_amount_in_cents>
			<quantity>1</quantity>
			<subscription_add_ons>
				<subscription_add_on>
					<unit_amount_in_cents>240</unit_amount_in_cents>
					<quantity>1</quantity>
					<add_on_code>HZ02B</add_on_code>
				</subscription_add_on>
			</subscription_add_ons>
		</subscription>
	</subscriptions>
</purchase>

And this is the method called

\Recurly_Purchase::invoice($purchaseAggregate->getPurchase(), $client);

So i would assume to get an error like addon not allowed but instead get this one:

  [Recurly_ValidationError] Next bill date is invalid.

So is there something wrong with my settings as i need to get more meaningful error messages.

[aaron-junot]

@azngeek I have confirmed the behavior you described. It appears that this is an error with the API and not the client libraries. I'm going to investigate further and let you know what the solution is.

[aaron-junot]

@azngeek I opened a ticket with the team who maintains that portion of the API. I will close out this issue with additional information when that team addresses that ticket. Thanks for pointing this out.

[azngeek]

Thanks for that .

[aaron-junot]

Hey there @azngeek! The team fixed this issue a couple months ago but I just found out today. Everything should have been fine since late March. If you see this problem again (or see this same error in your logs from April until now), please let us know and we can re-open the issue and take a look at it. Thanks!