Eternity Ring bugged

[Zumi]

The issue I am having is my Eternity Ring has become bugged, it says obtaining signature instead of my eternal bond partner's name Asunaru Sakura. She did not change her name or transfer servers so there should be no reason why my Eternity Ring says obtaining signature.

This is a serious issue because these rings cost $40.00 total when we got them since we did the most expensive wedding plan.

Photo of the issue below.



ISP:
Comcast

Type of Internet Connection:
Cable

Internet Connection Speed:
60 mbps

Date & Time:
First noticed the bug 1/12/2016

Frequency:
Always

World:
Sargatanas

Character Name:
Which character did the issue occur with?
Zumi Kasumi

Class/Level:
Paladin lv 60

Party or Solo:
solo

Race:
Au Ra Female

In-Game Time: Always

Area and Coordinates:
Old Gridania 14, 9

Housing:
None

[Ashelia_Ferron]

The ring doesn't show your partner's name, it's the name of whomever crafted the ring.

So, unless your partner was the one that made it, it will display the crafter's name, and if they made any changes, then Obtaining Signature will be displayed

[Asunaru]

no problems on my side,your name is visible on my ring

[Yukileonhart]

Lodestone sittings maybe ??!?

[Zumi]

The ring doesn't show your partner's name, it's the name of whomever crafted the ring.

So, unless your partner was the one that made it, it will display the crafter's name, and if they made any changes, then Obtaining Signature will be displayed

No Eternity Rings show the name of the person you married.

An update on the issue upon logging in today it fixed itself. But still this is an issue with it randomly changing to obtaining signature.

[Nezerius]

It's not a bug, OP, it just means the server wasn't able to read the other player's name at that time. It's something that fixes itself after a bit, assumingly when the other player logs on.

It was mentioned in the 3.0 patch notes:

[2.0] The message "Obtaining Signature" will now be displayed when an item's signature is unable to be read.

[Mholito]

It happens whenever someone hasn't logged on since maintenance.