Port forwarding bug

This is one of the most annoying bugs I've ever encountered.
Since being forced to do port forwarding through your app ([Edited: "Language"]) I have dealt with this persistent bug.

What's happening is I create a port forwarding rule, and it changes on it's own.
I assign the port forward rule to a static IP on my network (my media server.) Which is an address ending in .11, and that will never change.

For the record, my subnet IP range only extends to .30. Anything with DHCP will never go over .30, but my server is static anyways and not using dhcp.

Here's where the bug kicks in. After creating the rule, given a random amount of time being hours to days, the rule will automatically switch itself to a .232 address (which can't and doesn't exist)
This wouldn't be that much of an issue, except I have to entirely recreate the rule from scratch because your garbage app doesn't even have the option to change the IP/device once the rule has been created.
I have to manually re-enter about 30 port forwards each time (I'm providing dozens of servers)

In short, an application bug on your end is causing my port forwarding rules to all revert to a .232 address

I also have to hit the delete button once for as many individual port rules exist within that rule. Should be one click, unless specifically targeting rules within the overall rule.

Wish I could use the old web gui that had zero issues, but nooo you greyed out the options to force me onto an app in order to advertise me packages I don't want.
It'd be nice if you could change the device or IP after creating the rule, and it's also be nice if the list gave me an IP address before creating the rule (right now 90% of the devices on my list are "generic Windows PC/Laptop" which is completely useless)
Amazing an internet provider worth billions can't spend a few bucks to properly develop an app. Networking and app development should be your two greatest skills, in that order, yet Xfi fails at both.