omar/MosisService
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
8cb3cf769d09e8371b6c185127e7f465a1697eac
MosisService/portal/internal/web/docs/troubleshooting.md

8.0 KiB
Raw Blame History

Troubleshooting

Solutions for common issues when developing Mosis apps.

Build Errors

"Invalid manifest: missing required field"

Your manifest.json is missing a required field.

Solution: Check these required fields:

{
  "id": "com.example.app",
  "name": "App Name",
  "version": "1.0.0",
  "version_code": 1,
  "entry": "assets/main.rml",
  "author": {
    "name": "Your Name",
    "email": "you@example.com"
  },
  "icons": {
    "128": "icon.png"
  }
}

"Invalid package ID format"

Package IDs must follow reverse domain notation.

Valid:

  • com.example.myapp
  • com.yourname.calculator
  • io.github.user.app

Invalid:

  • myapp (needs domain prefix)
  • Com.Example.App (must be lowercase)
  • com..app (no double dots)
  • com.app. (can't end with dot)

"Entry point not found"

The entry file specified in manifest doesn't exist.

Solution: Verify the path:

"entry": "assets/main.rml"

Check that assets/main.rml exists relative to your manifest file.

"Icon not found"

An icon file specified in manifest doesn't exist.

Solution:

  1. Check file paths are correct
  2. Ensure files exist
  3. Use forward slashes in paths
"icons": {
  "128": "icons/icon-128.png"
}

"Package too large"

Package exceeds the 10MB limit.

Solutions:

  • Compress images (use TGA or optimized PNG)
  • Remove unused assets
  • Move large files to external CDN
  • Check for accidentally included files

Runtime Errors

"attempt to index nil value"

You're accessing a property on a nil variable.

Common causes:

  1. Element not found:
-- Bad
local elem = document:GetElementById("typo")
elem.inner_rml = "Hello"  -- Error: elem is nil

-- Good
local elem = document:GetElementById("correct-id")
if elem then
    elem.inner_rml = "Hello"
end
  1. Table key doesn't exist:
-- Bad
local data = json.decode(response.body)
print(data.user.name)  -- Error if user is nil

-- Good
if data and data.user then
    print(data.user.name)
end

"attempt to call nil value"

You're calling a function that doesn't exist.

Common causes:

  1. Typo in function name:
-- Bad: navigateto (lowercase t)
navigateto("settings")

-- Good
navigateTo("settings")
  1. Missing permission:
-- Error if 'network' permission not declared
http.get(url, callback)

"Permission denied"

You're using an API without the required permission.

Solution: Add permission to manifest:

"permissions": ["storage", "network"]

"Network request failed"

HTTP request couldn't complete.

Common causes:

  1. No network permission:
"permissions": ["network"]
  1. Invalid URL:
-- Bad: missing protocol
http.get("api.example.com/data", callback)

-- Good
http.get("https://api.example.com/data", callback)
  1. HTTP not allowed (HTTPS only):
-- Bad
http.get("http://example.com/data", callback)

-- Good
http.get("https://example.com/data", callback)
  1. CORS error: The server doesn't allow cross-origin requests. Contact the API provider or use a CORS proxy.

"Storage quota exceeded"

You've exceeded the 5MB storage limit.

Solution:

  • Clear unnecessary data: storage.clear()
  • Use selective removal: storage.remove("large-key")
  • Store only essential data
  • Consider using network storage for large data

UI Issues

Element not displaying

Check:

  1. Display not set to none:
/* Element might be hidden */
.element {
    display: none;  /* Remove this */
}
  1. Size is zero:
.element {
    width: 0;   /* Add dimensions */
    height: 0;
}
  1. Element is off-screen:
.element {
    position: absolute;
    left: -1000dp;  /* Move to visible area */
}
  1. Z-index issues:
.element {
    z-index: 1;  /* Bring to front */
}

Click events not working

Check:

  1. Function exists:
<button onclick="handleClick()">Click</button>

-- Make sure function is defined
function handleClick()
    print("Clicked!")
end

  1. Element is overlapped: Another element might be blocking clicks. Check z-index and position.

  2. Element has pointer-events: none:

.element {
    /* Remove this */
    pointer-events: none;
}

Styles not applying

Check:

  1. Stylesheet is linked:
<head>
    <link type="text/rcss" href="styles.rcss"/>
</head>
  1. Selector is correct:
/* Class selector needs dot */
.my-class { }

/* ID selector needs hash */
#my-id { }

/* Tag selector has no prefix */
button { }
  1. Specificity issues: More specific selectors override less specific ones:
/* Less specific */
button { color: blue; }

/* More specific - wins */
.btn.primary { color: red; }
  1. Units are correct:
/* Use dp units */
padding: 12dp;

/* Not px on mobile */
padding: 12px;  /* May not work correctly */

Layout breaks on different screens

Solutions:

  1. Use dp units instead of px:
padding: 16dp;  /* Scales properly */
  1. Use flexbox:
.container {
    display: flex;
    flex-direction: column;
}
  1. Use percentage widths:
.card {
    width: 90%;
    max-width: 400dp;
}

Text is cut off

Solutions:

  1. Allow wrapping:
.text {
    word-break: break-word;
}
  1. Add overflow scrolling:
.container {
    overflow: auto;
}
  1. Use ellipsis (if supported):
.text {
    text-overflow: ellipsis;
    overflow: hidden;
    white-space: nowrap;
}

Designer Issues

Hot reload not working

Solutions:

  1. Save the file - Changes only reload on save
  2. Check file is in watch path
  3. Restart designer - Sometimes needed after many changes
  4. Check for syntax errors - Invalid files may not reload

Designer crashes on startup

Solutions:

  1. Check file paths:
# Make sure path exists
mosis-designer.exe ../assets/main.rml
  1. Try a simple file first:
<rml>
<head><title>Test</title></head>
<body><p>Hello</p></body>
</rml>

  1. Check for missing assets: Images or fonts that don't exist can cause crashes.

  2. Update graphics drivers: The designer uses OpenGL which requires up-to-date drivers.

Rendering looks different on device

Common causes:

  1. Font differences - Ensure fonts are bundled
  2. DPI scaling - Use dp units consistently
  3. Color profiles - Use standard sRGB colors

Submission Issues

"Version code must be higher"

Each new version needs a higher version_code.

Solution:

{
  "version": "1.0.1",
  "version_code": 2  // Increment from previous
}

"Signature verification failed"

Your package signature is invalid.

Solutions:

  1. Rebuild the package:
mosis build
  1. Check signing key is registered:
mosis keys list
  1. Re-register your key if needed:
mosis keys register ~/.mosis/keys/production.pub

"Review rejected"

Check the rejection reason in your dashboard. Common issues:

Reason Solution
Inappropriate content Remove violating content
Misleading description Update description to match functionality
Crashes on launch Fix startup errors
Missing privacy policy Add privacy policy for data-collecting apps
Impersonation Don't copy other apps

Getting More Help

Check Logs

Designer logs:

mosis-designer.exe app.rml --log debug.log

Lua errors:

-- Add error handling
local success, err = pcall(function()
    -- Your code
end)
if not success then
    print("Error:", err)
end

Search Issues

Check if others have encountered the same issue:

  • Developer forum
  • GitHub issues
  • Stack Overflow (tag: mosis)

Contact Support

If you're still stuck:

  1. Gather error messages and logs
  2. Create minimal reproduction case
  3. Submit through developer portal support

See Also

Reference in New Issue View Git Blame Copy Permalink