A man looks at his Apple iPad in front an Apple logo outside an Apple store in downtown Shanghai
A man looks at his Apple iPad in front an Apple logo outside an Apple store in downtown Shanghai March 16, 2012. Reuters/Aly Song

The iMessage introduced by Apple is highly potential and easy as it allows the users to be in touch with their loved ones all the time through messages without paying for it.

These messages are not counted against users monthly plan texting schemes and it can even send messages to overseas users at no cost. If a user owns multiple Apple devices, the iMessage provides the benefit of showing messages to all these devices such as an iPad or a MacBook just by setting it up as per the process.

But recently an unwanted bug has been discovered that is causing problems to former iMessage users who have switched from an iPhone to another smartphone. The bug prevents users from sending and receiving messages from friends and family.

Apple has acknowledged the bug within its iMessage system and ensures to fix it as soon as possible.

Apple has set up a support page ensuring that the former iPhone owners follow the process and continue to send standard text. Even if the user changes from iPhone to another device, the cellular phone number might still be registered with iMessage.

To deregister the phone number from iMessage, one needs to go to Settings, tap on the Messages option and then turn off the iMessage selection.

Turning off iMessage should ensure that all messages are sent in a standard way and can get through all other non-Apple devices as well.

But a Canadian woman, former iPhone owner is so displeased with her experience that she has filed a lawsuit against Apple over the problem.

The woman is seeking a class action status for the suit and claims Apple failed to disclose that switching from iPhone to another device would cause interference in the text messages.

Apple commented that it started fixing the problem

"We recently fixed a server-side iMessage bug which was causing an issue for some users, and we have an additional bug fix in a future software update," Apple told Re/code. "For users still experiencing an issue, please contact AppleCare."