Bug 150171 - Apple Silicon version of LibreOffice appears as an IOS app not a "Universal" app.
Summary: Apple Silicon version of LibreOffice appears as an IOS app not a "Universal" ...
Status: RESOLVED DUPLICATE of bug 144200
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.3.5.2 release
Hardware: ARM macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-07-27 16:35 UTC by David Snow
Modified: 2022-12-18 17:18 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
screenshot (786.19 KB, image/png)
2022-07-27 16:36 UTC, David Snow
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Snow 2022-07-27 16:35:51 UTC
Description:
Most macOS applications that have been updated from Intel are compiled so that they are "Universal" and can run on either Intel or Arm. It is also possible to install IOS applications on a M1 MacBook since both the iPad and Macbook use Arm processors.

LibreOffice is the first and ONLY app that I have run across that doesn't come from the IOS-App-Store that is listed as IOS!

Why isn't LibreOffice being compiled as a Universal app?

Steps to Reproduce:
1. Go to Apple menu "About this Mac"
2. Go to "System Report"
3. Select Software / Applications
4. Find LibreOffice and compare with other applications

Actual Results:
LibreOffice is an IOS Application

Expected Results:
It should be a Universal Appl


Reproducible: Always


User Profile Reset: No



Additional Info:
See attached screen shot.

Also in Ventura 13.0 Apple moved the system report. Finding it is a treat!
Comment 1 David Snow 2022-07-27 16:36:42 UTC
Created attachment 181448 [details]
screenshot
Comment 2 David Snow 2022-07-27 16:37:39 UTC
If LibreOffice is actually an IOS application when please tell me how I can load it on my iPad?
Comment 3 Michael Warner 2022-07-28 12:55:13 UTC
This bug has already been reported.

*** This bug has been marked as a duplicate of bug 144200 ***