Jump to content
  • It takes you out of the registry in private

    • Status: Closed Priority: Normal

    On some occasions the application takes me out of the registry when I try to rank a person, just as it happens when I try to speak to the private person.


    It is not the first time that happens to me.

    User Feedback

    Recommended Comments

    What happens in itself is that sometimes I open a private user and automatically pulls me out of the app if I throw some kind of error and it has happened several times I think it may be some kind of system error in the app because in other devices it has also happened to me

    Specifically IOS (Apple) & Android

    → Android Tablet Canaima

    • It has an Intel Atom Z2550 1.2Ghz Dual Core processor, its mid-range processor is complemented by a 1GB RAM.

    • integrated software from Intel Education Software,

    • Operating system is Android 4.2.2

    Apple (iphone 5s) GSM A1533

    • A7 dual-core processor at 1.3 GHz / 64 bits

    • 1 GB of RAM

    • Resolution: 640 x 1136 pixels (16: 9 format), density of 326 ppi

    • CPU: SoC Apple A7 dual-core 1.3 GHz, with 64-bit architecture based on ARMv8 and M7 motion coprocessor

    RAM: 1 GB LPDDR3

    GPU: Imagination Technologies PowerVR G6430 quad-core at 200 MHz

    Share this comment

    Link to comment
    Share on other sites

    Thank you for the detailed information @PedroAccount.


    In order to pinpoint the issue could you answer me a few more questions:

    So if i understood you correctly, you start a p.chat with an user (or what do you mean by "open a private user"?) and the app crashes, giving you an error - is that right?


    Could you tell me what the error message says?

    Are you able to provide a gif? 

    Share this comment

    Link to comment
    Share on other sites

    @PedroAccount You may want to check out if this still happens with the latest version (you have to download it).


    Let me know about the outcome.


    If the issue still persists for you, please see my previous post.



    Share this comment

    Link to comment
    Share on other sites

    Since this doesn't seem to be a bug and/or a good amount of time has passed without any further response, this will be closed.


    If you'd clash into this again, feel free to open a new bug, giving as much detail as you can, including screenshots/gifs.


    Thank you!

    Share this comment

    Link to comment
    Share on other sites

    This is now closed for further comments

  • Priority Definitions


    Trivial The issue is considered low priority.

    Normal This is the default priority.

    High A feature or service is not working properly, and it impacts a lot of people. The issue should be fixed in the near future.

    Critical The issue is show-stopping, meaning that a certain feature or service is completely broken with no available workaround. The issue impacts a lot of people and requires immediate repair.

  • Status Definitions


    Open The issue is pending, or we are still working on the issue.

    Fixed The issue has been resolved. The fix may not be immediately noticeable and may be released in a future version or update.

    Closed This record is either not considered an issue or is better suited as a suggestion. If it is an issue, it may not be reproducible.

    Won't Fix The issue will not be fixed because it is too low in priority. The issue is very minor. The resources required to fix the issue cannot justify the benefits received from fixing the issue. This means the issue is closed.


Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.