ZXing无法输出PNG文件：升级macOS High Sierra后代码运行异常

Hey Martin, sorry to hear your ZXing PNG generation broke after upgrading to macOS High Sierra—total bummer when a working setup goes sideways post-update! Let’s walk through some targeted troubleshooting steps to get this sorted:

• 检查系统安全权限
  macOS High Sierra tightened up access controls for system resources, especially for tools handling graphics. If your code uses Java (the most common ZXing implementation), the JVM might be blocked from accessing graphics subsystems:

  • Head to System Preferences > Security & Privacy > Privacy, then make sure your IDE/terminal or Java runtime has permission under Full Disk Access or Files and Folders.
  • If you see a prompt about blocked system software from Oracle, click "Allow" in the Security pane—this is a common gotcha for Java runtimes on High Sierra.

• Verify ZXing library compatibility
  Older ZXing versions might not play nice with High Sierra’s updated frameworks:

  • Update to the latest stable ZXing release. For Java projects, refresh your Maven/Gradle dependency to the newest artifact.
  • If you’re using a native ZXing binding (Swift/Obj-C), recompile the library locally against the High Sierra SDK to fix architecture or framework mismatches.

• Test image I/O independently
  ZXing relies on system image libraries to write PNGs. Let’s rule out issues with ImageIO itself:
  For Java, run this quick test outside of ZXing:

  import javax.imageio.ImageIO;
  import java.awt.image.BufferedImage;
  import java.io.File;
  
  public class ImageIOTest {
      public static void main(String[] args) throws Exception {
          BufferedImage testImg = new BufferedImage(100, 100, BufferedImage.TYPE_INT_RGB);
          ImageIO.write(testImg, "PNG", new File("/tmp/test-zxing.png"));
          System.out.println("Test PNG written successfully!");
      }
  }
  

  If this fails, the problem is with your Java environment’s ImageIO setup, not ZXing. Try reinstalling your JDK or switching to OpenJDK instead of Oracle’s distribution.

• Check native library links (if using non-Java ZXing)
  If you’re working with a native ZXing build, the system upgrade might have broken dynamic library paths. Run this command on your binary to check for missing dependencies:

  otool -L /path/to/your/zxing/binary
  

  Look for entries marked "not found"—you’ll need to update those paths or recompile the library against High Sierra.

• Get a full error trace
  Your current error message is cut off at Error: Code:—wrap your ZXing code in a try-catch block to print the full stack trace. For Java:

  try {
      // Your existing ZXing PNG generation code here
  } catch (Exception e) {
      e.printStackTrace();
  }
  

  This will show exactly where the failure happens—whether it’s during barcode encoding, image writing, or a system-level permission block.

内容的提问来源于stack exchange，提问作者martinjack